linux-kernel - Re: [BUG] File system corruption with 4.4-rc3 and beyond

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]

Message-ID: <20151222202321.5166297e@gandalf.local.home>
Date:	Tue, 22 Dec 2015 20:23:21 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Ellerman <mpe@...erman.id.au>,
	Mark Salter <msalter@...hat.com>,
	Laurent Dufour <ldufour@...ux.vnet.ibm.com>,
	Ming Lei <ming.lei@...onical.com>, Jens Axboe <axboe@...com>,
	linux-block@...r.kernel.org
Subject: Re: [BUG] File system corruption with 4.4-rc3 and beyond

On Tue, 22 Dec 2015 16:17:25 -0800
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> We *just* fixed this. It was pretty subtle, and the debugging went on
> for several days. But the fixed got applied to the block tree earlier
> today, and I just pulled it only 15 minutes ago and pushed it out just
> now.

Just my luck. I've spent probably 5 days or more on this thinking it
was a hardware issue. :-/

> 
> So check current -git, it should work for you.
> 
> (And if you care about the particular fix: it's commit 23688bf4f830:
> "block: ensure to split after potentially bouncing a bio").

Thanks, I do care. I'll be backporting this commit to the kernel I test
for my own code.

> 
> And yes, the way to trigger it seems to be to run a 32-bit kernel and have PAE.

Yep, that's exactly the environment that I saw this in.

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