From: Russell Coker <russell@coker.com.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops on 2.4.22 when mounting from broken NFS server
Date: Tue, 16 Sep 2003 02:21:34 +1000 [thread overview]
Message-ID: <200309160221.34621.russell@coker.com.au> (raw)
In-Reply-To: <shs3ceyjc4k.fsf@charged.uio.no>
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
next prev parent reply other threads:[~2003-09-15 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 9:38 Russell Coker
2003-09-15 12:47 ` Russell Coker
2003-09-15 15:38 ` Trond Myklebust
2003-09-15 15:47 ` Trond Myklebust
2003-09-15 16:21 ` Russell Coker [this message]
2003-09-15 17:01 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309160221.34621.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®