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: <44C66296.2010109@sandeen.net>
Date:	Tue, 25 Jul 2006 13:27:34 -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:

> Putting it another way,
>  ext3_get_dentry reject certain inums that are known to be a problem.
>  ext2_get_dentry allows only those inums that could possibly be ok.
> 
> So if you (anyone) prefer one approach over the other, making the
> change so they both fs take the same approach would be trivial.

I like the 2nd approach - seems simpler, takes care of everything in 
->get_dentry, right?.  But I think your original patch is all that will 
work for 2.4 kernels...

-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/