linux-kernel - Re: Bad ext3/nfs DoS bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44C906CB.8050100@sandeen.net>
Date:	Thu, 27 Jul 2006 13:32:43 -0500
From:	Eric Sandeen <sandeen@...deen.net>
To:	Neil Brown <neilb@...e.de>
CC:	Andrew Morton <akpm@...l.org>, Theodore Tso <tytso@....edu>,
	jack@...e.cz, 20@...ingley.org, marcel@...tmann.org,
	linux-kernel@...r.kernel.org, sct@...hat.com, adilger@...sterfs.com
Subject: Re: Bad ext3/nfs DoS bug

Neil Brown wrote:
> On Wednesday July 26, sandeen@...deen.net wrote:

>> Hm, with this, ext3.ko has a new dependency on exportfs.ko.  Is that 
>> desirable/acceptable?
> 
> Drat, you're right.
> No, I don't think that is what we want.
> I'll do it differently in a day or so.

Would moving export_iget into fs/inode.c & exporting it from there be a 
reasonable way to go?  At least ext2 & ext3 both have this need (prevent 
nfs access to special inodes) so putting the bulk of what they need for 
get_dentry (i.e. export_iget) somewhere common seems like a decent 
option to me.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/