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: <20080211113652.GA3833@skywalker> Date: Mon, 11 Feb 2008 17:06:52 +0530 From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> To: tytso@....edu, cmm@...ibm.com Cc: linux-ext4@...r.kernel.org Subject: Re: [PATCH] ext4: Don't claim block from group which has corrupt bitmap On Mon, Feb 11, 2008 at 05:00:18PM +0530, Aneesh Kumar K.V wrote: > In ext4_mb_complex_scan_group, if the extent length of the newly > found extentet is greater than than the total free blocks counted > in group info, break without claiming the block. > > Document different ext4_error usage, explaining the state with which we > continue if we mount with errors=continue > > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com> > --- > fs/ext4/mballoc.c | 16 +++++++++++++++- > 1 files changed, 15 insertions(+), 1 deletions(-) This was actually part of the version 2 of the patch ext4_avoid_panic_in_case_of_corrupted_bitmap.patch. But we missed it in the last update. So sending it as a separate patch. -aneesh - 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