From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.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
Subject: Re: [BUG] File system corruption with 4.4-rc3 and beyond
Date: Tue, 22 Dec 2015 20:23:21 -0500 [thread overview]
Message-ID: <20151222202321.5166297e@gandalf.local.home> (raw)
In-Reply-To: <CA+55aFz4hJ0UeRuO2_sQgyQcz2-NLsdBNCyjhSOGrWbk2gcc8w@mail.gmail.com>
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
prev parent reply other threads:[~2015-12-23 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 0:09 Steven Rostedt
2015-12-23 0:16 ` Jens Axboe
2015-12-23 1:09 ` Steven Rostedt
2015-12-23 1:20 ` Steven Rostedt
2015-12-23 2:44 ` Steven Rostedt
2015-12-23 1:14 ` Ming Lei
2015-12-23 0:17 ` Linus Torvalds
2015-12-23 1:23 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151222202321.5166297e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=mpe@ellerman.id.au \
--cc=msalter@redhat.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®