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: Wed, 17 Oct 2007 21:09:25 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Jan Kara <jack@...e.cz> Cc: cmm@...ibm.com, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, sho@...s.nec.co.jp, clameter@....com Subject: Re: [PATCH 2/2] ext2: Avoid rec_len overflow with 64KB block size On Thu, 11 Oct 2007 13:18:49 +0200 Jan Kara <jack@...e.cz> wrote: > With 64KB blocksize, a directory entry can have size 64KB which does not fit > into 16 bits we have for entry lenght. So we store 0xffff instead and convert > value when read from / written to disk. btw, this changes ext2's on-disk format. a) is the ext2 format documented anywhere? If so, that document will need updating. b) what happens when an old ext2 driver tries to read and/or write this directory entry? Do we need a compat flag for it? c) what happens when old and new ext3 or ext4 try to read/write this directory entry? - 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