| 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: Tue, 16 Aug 2011 23:12:27 -0400 From: Bob Copeland <me@...copeland.com> To: Al Viro <viro@...iv.linux.org.uk> Cc: Josh Boyer <jwboyer@...hat.com>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: Oops in minixfs_statfs On Tue, Aug 16, 2011 at 10:18 PM, Al Viro <viro@...iv.linux.org.uk> wrote: > I *think* that what's happening in your case is that we have more blocks > for block bitmap than we would need to hold all bits. That would explode > in exactly such a way, but I'd like to see confirmation; what arguments > does your count_free() actually get? The last two arguments, that is... Sounds like it, Josh posted this output before: [ 516.859103] imap_blocks 7 zmap_blocks 7 firstdatazone c11 log_zone_size 0 max_size 7fffffff magic 4d5a nzones 3001c blocksize: 1000 So there are 7 blocks in the zone bitmap but only 0x3001c - 0xc11 = 193547 zones to allocate, which would fit in 6 blocks. -- Bob Copeland %% www.bobcopeland.com -- 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