stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Eddie Chapman <eddie@ehuk.net>,
	gregkh@linuxfoundation.org, colyli@suse.de, mlyle@lyle.org
Cc: awolf@lenovo.com, bcache@lists.ewheeler.net,
	hurikhan77@gmail.com, kent.overstreet@gmail.com,
	nix@esperi.org.uk, tang.junhui@zte.com.cn,
	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: Mon, 27 Nov 2017 10:01:41 -0700	[thread overview]
Message-ID: <2bc54d3d-0fbe-0e8e-97b5-a317972d0ad3@kernel.dk> (raw)
In-Reply-To: <704d1c65-b032-314b-3ad1-e87229dc655a@ehuk.net>

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
>>
>> to the 4.9-stable tree which can be found at:
>>      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>       bcache-only-permit-to-recovery-read-error-when-cache-device-is-clean.patch
>> and it can be found in the queue-4.9 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
> 
> 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.

-- 
Jens Axboe

  reply	other threads:[~2017-11-27 17:01 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 [this message]
     [not found]     ` <CAJ+L6qcud8-aXziGAODBSA-9d2gaZmnx2PbQEyJwbCHUD1a2YQ@mail.gmail.com>
2017-11-28  9:06       ` Greg KH
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=2bc54d3d-0fbe-0e8e-97b5-a317972d0ad3@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=awolf@lenovo.com \
    --cc=bcache@lists.ewheeler.net \
    --cc=colyli@suse.de \
    --cc=eddie@ehuk.net \
    --cc=gregkh@linuxfoundation.org \
    --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 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).