linux-ext4 - Re: Oops with ext4 from 2.6.27-rc3

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Aug 2008 18:01:00 -0400
From:	Theodore Tso <tytso@....edu>
To:	Christian Hesse <mail@...rm.de>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Oops with ext4 from 2.6.27-rc3

On Wed, Aug 13, 2008 at 11:07:06PM +0200, Christian Hesse wrote:
> 
> Please look at the bottom of my last two mails... That was with your patch 
> applied.

Sorry, I missed it.  The new BUG seems to be a bug in the delayed
allocation code, specifically here, in fs/ext4/inode.c:ext4_da_release_space():

	   /* figure out how many metablocks to release */
	   BUG_ON(mdb > EXT4_I(inode)->i_reserved_meta_blocks);
	   mdb_free = EXT4_I(inode)->i_reserved_meta_blocks - mdb;

I've quickly looked at the code, and how i_reserved_meta_blocks gets
updated, and nothing *obviously* wrong is jumping out at me.  Anyone
else have time to investigate this a bit more deeply?

     	       	  	      	     	 - Ted

--
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