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
| ||
|
Date: Mon, 3 May 2010 12:31:11 +0530 From: "Amit K. Arora" <aarora@...ux.vnet.ibm.com> To: Christoph Hellwig <hch@...radead.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Nikanth Karthikesan <knikanth@...e.de>, coly.li@...e.de, Nick Piggin <npiggin@...e.de>, Alexander Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org, "Theodore Ts'o" <tytso@....edu>, Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org, Eelis <opensuse.org@...tacts.eelis.net>, Amit Arora <aarora@...ibm.com> Subject: Re: [PATCH] Prevent creation of files larger than RLIMIT_FSIZE using fallocate On Sat, May 01, 2010 at 06:18:46AM -0400, Christoph Hellwig wrote: > On Sat, May 01, 2010 at 12:34:26PM +0530, Amit K. Arora wrote: > > Agreed. How about doing this check in the filesystem specific fallocate > > inode routines instead ? For example, in ext4 we could do : > > That looks okay - in fact XFS should already have this check because > it re-uses the setattr implementation to set the size. You are right. I have written a test and it passes on XFS, but fails on ext4. > Can you submit an xfstests testcase to verify this behaviour on all > filesystems? Sure. Its ready and is under test. Will post shortly.. -- Regards, Amit Arora -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists