Messages in this thread | | | From | Russell Coker <> | Subject | Re: Oops on 2.4.22 when mounting from broken NFS server | Date | Tue, 16 Sep 2003 02:21:34 +1000 |
| |
On Tue, 16 Sep 2003 01:38, Trond Myklebust wrote: > Without a tcpdump, there's no way to know why this dumped. In what way > was the NFS server broken, and exactly how do you expect the Linux NFS > client to protect you against it?
The NFS server was unable to read the directories it was exporting, so it would allow the mount command but then fail to do anything.
I expect the NFS client to behave sensibly in the face of all possible server errors, including the possibility of a hostile NFS server.
> BTW: that Oops you posted looked very much like a memory corruption > problem. Were you running vanilla 2.4.22 on the client, or was it too > patched?
It was also patched. I will try and reproduce the error with an unpatched kernel and a tcpdump running.
-- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |