From: Liu Bo <bo.li.liu@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] Btrfs: fix crash on endio of reading corrupted block
Date: Sat, 23 Aug 2014 11:53:58 +0800 [thread overview]
Message-ID: <20140823035357.GB28391@localhost.localdomain> (raw)
In-Reply-To: <53F7627D.3060405@redhat.com>
On Fri, Aug 22, 2014 at 10:32:13AM -0500, Eric Sandeen wrote:
> On 8/20/14, 3:51 AM, Liu Bo wrote:
> > The crash is
> >
> > ------------[ cut here ]------------
> > kernel BUG at fs/btrfs/extent_io.c:2124!
> > invalid opcode: 0000 [#1] SMP
>
> ...
>
> > ---
> > v2:
> > - Improve the commit log to be clear, suggested by Eric.
>
> Well, I had specifically asked for it to include details on when
> the regression occurred, but didn't get that... ;)
>
> If you state that it's a regression, people may start wondering
> if their kernels are vulnerable, how far back into -stable it
> should go, which distros should pick up the fix, etc. If you
> don't say when it regressed, we're all left wondering...
Oh yeah, now I get it :)
thanks,
-liubo
>
> Thanks,
>
> -Eric
>
next prev parent reply other threads:[~2014-08-23 3:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:33 [PATCH] Btrfs: fix crash on endio of reading corrupted block Liu Bo
2014-08-19 19:49 ` Chris Mason
2014-08-19 21:42 ` Eric Sandeen
2014-08-20 8:20 ` Liu Bo
2014-08-20 8:51 ` [PATCH v2] " Liu Bo
2014-08-22 15:32 ` Eric Sandeen
2014-08-23 3:53 ` Liu Bo [this message]
2014-08-23 3:59 ` Liu Bo
2014-08-23 4:00 ` [PATCH v3] " Liu Bo
2014-09-02 20:17 ` Chris Murphy
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=20140823035357.GB28391@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).