From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Lyle <mlyle@lyle.org>
Cc: Jens Axboe <axboe@kernel.dk>, Eddie Chapman <eddie@ehuk.net>,
Coly Li <colyli@suse.de>,
awolf@lenovo.com, Eric Wheeler <bcache@lists.ewheeler.net>,
Kai Krakow <hurikhan77@gmail.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Nix <nix@esperi.org.uk>, Junhui Tang <tang.junhui@zte.com.cn>,
stable <stable@vger.kernel.org>
Subject: Re: Patch "bcache: only permit to recovery read error when cache device is clean" has been added to the 4.9-stable tree
Date: Tue, 28 Nov 2017 10:06:24 +0100 [thread overview]
Message-ID: <20171128090624.GA30025@kroah.com> (raw)
In-Reply-To: <CAJ+L6qcud8-aXziGAODBSA-9d2gaZmnx2PbQEyJwbCHUD1a2YQ@mail.gmail.com>
On Mon, Nov 27, 2017 at 09:35:02AM -0800, Michael Lyle wrote:
> On Mon, Nov 27, 2017 at 9:01 AM, Jens Axboe <axboe@kernel.dk> wrote:
>
> > On 11/27/2017 09:45 AM, Eddie Chapman wrote:
> > > On 27/11/17 16:06, gregkh@linuxfoundation.org wrote:
> > >>
> > >> This is a note to let you know that I've just added the patch titled
> > >>
> > >> bcache: only permit to recovery read error when cache device is
> > clean
> >
>
>
> > > Hi Greg,
> > >
> > > This patch is an important fix for a possible data corruption issue, but
> > > it also introduces a bug that can produce read errors under certain
> > > circumstances. The issue introduced by this patch is not as severe as
> > > the issue it fixes, but can lead to e.g. upper layer fs remounting read
> > > only. In my environment upper layer handled it badly and indirectly
> > > resulted in data loss (not directly bcache's fault of course).
> > >
> > > Michael Lyle CC'd the stable list with a follow up fix for the issue
> > > introduced by this patch, on 24th Nov, subject "bcache: recover data
> > > from backing when data is clean".
> > >
> > > However, the followup fix is not in Linus' tree yet, only in Michael's.
> > > I guess that means you can't pick it up yet. Never-the-less I felt it
> > > important to point this out here.
> >
> > It's commit e393aa2446150536929140739f09c6ecbcbea7f0 in my tree and will
> > go upstream shortly - but yes, probably should not add this one, before
> > both can be pulled in.
>
>
> Thanks everyone for the quick reply on this. I agree.
Ok, I've dropped this patch from all of the stable queues for now.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-28 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 16:06 Patch "bcache: only permit to recovery read error when cache device is clean" has been added to the 4.9-stable tree gregkh
2017-11-27 16:45 ` Eddie Chapman
2017-11-27 17:01 ` Jens Axboe
[not found] ` <CAJ+L6qcud8-aXziGAODBSA-9d2gaZmnx2PbQEyJwbCHUD1a2YQ@mail.gmail.com>
2017-11-28 9:06 ` Greg KH [this message]
2017-12-04 10:27 ` Greg KH
2017-12-04 23:45 ` Eddie Chapman
2017-12-05 7:49 ` Greg KH
2017-12-05 14:30 ` Greg KH
2017-12-05 17:49 ` Michael Lyle
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 14:30 gregkh
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=20171128090624.GA30025@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=awolf@lenovo.com \
--cc=axboe@kernel.dk \
--cc=bcache@lists.ewheeler.net \
--cc=colyli@suse.de \
--cc=eddie@ehuk.net \
--cc=hurikhan77@gmail.com \
--cc=kent.overstreet@gmail.com \
--cc=mlyle@lyle.org \
--cc=nix@esperi.org.uk \
--cc=stable@vger.kernel.org \
--cc=tang.junhui@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.