linux-ext4 - Re: ext4 metadata corruption bug?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20140806085345.GM25902@dot.freshdot.net>
Date:	Wed, 6 Aug 2014 10:53:45 +0200
From:	Sander Smeenk <ssmeenk@...shdot.net>
To:	linux-ext4@...r.kernel.org
Subject: Re: ext4 metadata corruption bug?

Quoting Theodore Ts'o (tytso@....edu):

> Are you folks still seeing ext4_mb_generate_buddy or
> ext4_mb_release_inode_pa EXT4-fs errors?
> 
> I think I may have found a fix for this problem.  Or at least, I've
> found one of the causes.  If we get a memory allocation failure from
> ext4_mb_new_inode_pa(), it can cause these errors.

Good to hear a probable cause was found. Unfortunately for this bug's
progress, i've switched to a newer kernel altogether since the 3.13
tree in Ubuntu has had a lot of other problems besides this
EXT4 ext_mb_generate_buddy issue.

With 3.15.0 i have not experienced any ext4 issues at all.

If you want me to, i would be willing to boot that VM in 3.13 with this
patch, but as said, it can take ages before the bug was triggered...

Thanks for your hard work.

-Sndr.
-- 
| > Because we read from top to bottom.
| > > Why should i start my email reply *below* the quoted text?
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7  FBD6 F3A9 9442 20CC 6CD2
--
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