MIME-Version: 1.0
In-Reply-To: <20151222190908.658e7fb7@gandalf.local.home>
References: <20151222190908.658e7fb7@gandalf.local.home>
Date: Tue, 22 Dec 2015 16:17:25 -0800
Message-ID: <CA+55aFz4hJ0UeRuO2_sQgyQcz2-NLsdBNCyjhSOGrWbk2gcc8w@mail.gmail.com>
Subject: Re: [BUG] File system corruption with 4.4-rc3 and beyond
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Michael Ellerman <mpe@ellerman.id.au>,
        Mark Salter <msalter@redhat.com>,
        Laurent Dufour <ldufour@linux.vnet.ibm.com>,
        Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@fb.com>,
        linux-block@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1107
Lines: 28

On Tue, Dec 22, 2015 at 4:09 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Since it seemed very reliable, I started my bisect. It came down to this
> patch:
>
> From 578270bfbd2803dc7b0b03fbc2ac119efbc73195 Mon Sep 17 00:00:00 2001
> From: Ming Lei <ming.lei@canonical.com>
> Date: Tue, 24 Nov 2015 10:35:29 +0800
> Subject: [PATCH] block: fix segment split

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.

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").

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

               Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/