| 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
| ||
|
Message-ID: <20120514230240.GZ5353@quack.suse.cz> Date: Tue, 15 May 2012 01:02:40 +0200 From: Jan Kara <jack@...e.cz> To: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@...il.com> Cc: Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH] Fix minixfs size check On Tue 15-05-12 00:33:52, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > On 15.05.2012 00:19, Jan Kara wrote: > > > On Sun 13-05-12 15:48:55, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > >> minixfs file size check is buggy and it doesn't allow creating a block which > >> can't be fully filled > > Umm, I'm not really minix expert but who'd set s_max_size to something > > which is not a multiple of block size? This looks rather artifical problem > > to me... > > > > The usual and natural limit comes from interpreting 32-bit size field as > signed or unsigned. So it's either 2G - 1 or 4G - 1. Neither of which is > a multiple of block size. Oh, right. Then your patch should be OK, just it's enough to cast one of the arguments to u64. And BTW looking at minix, it should also set s_maxbytes to s_max_size. Otherwise it will be always limited by MAX_NON_LFS which is 2^31-1. Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- 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/
Powered by blists - more mailing lists