From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 2] knfsd: Don't allow bad file handles to cause extX to go readonly
Date: Fri, 28 Jul 2006 10:31:20 +1000 [thread overview]
Message-ID: <20060728102713.15132.patches@notabene> (raw)
Currently, and file handle with a bad inode number in it can cause
ext2 to go to readonly (as it looks like a corrupted filesystem)
and could allow remote access to ext3 special files like the journal.
These patches give ext2/3 their own get_dentry method which checks the
inode number early before other bits of the code can be freaked out by
it.
These are revised versions of earlier patches. Rather than exporting
export_iget, we open code it and simplify it slightly. This avoids
and extra module dependancy.
NeilBrown
To follow:
[PATCH 001 of 2] knfsd: Have ext2 reject file handles with bad inode numbers early.
[PATCH 002 of 2] knfsd: Make ext3 reject filehandles referring to invalid inode numbers
next reply other threads:[~2006-07-28 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 0:31 NeilBrown [this message]
2006-07-28 0:31 ` [PATCH 001 of 2] knfsd: Have ext2 reject file handles with bad inode numbers early NeilBrown
2006-07-28 0:31 ` [PATCH 002 of 2] knfsd: Make ext3 reject filehandles referring to invalid inode numbers NeilBrown
2006-07-28 13:33 ` [NFS] [PATCH 000 of 2] knfsd: Don't allow bad file handles to cause extX to go readonly Christoph Hellwig
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=20060728102713.15132.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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