Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1297164 > unrolled thread

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

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [BUG] File system corruption with 4.4-rc3 and beyond Linus Torvalds <torvalds@linux-foundation.org> - 2015-12-23 01:20 +0100
    Re: [BUG] File system corruption with 4.4-rc3 and beyond Steven Rostedt <rostedt@goodmis.org> - 2015-12-23 02:30 +0100

#1297164 — Re: [BUG] File system corruption with 4.4-rc3 and beyond

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/

[toc] | [next] | [standalone]

#1297204

On Tue, 22 Dec 2015 16:17:25 -0800
Linus Torvalds <torvalds@linux-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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web