From: Jens Axboe <axboe@kernel.dk>
To: Michael Lyle <mlyle@lyle.org>,
Campbell Steven <casteven@gmail.com>,
Pavel Goran <via-bcache@pvgoran.name>
Cc: linux-bcache@vger.kernel.org,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: Regression in 4.14: wrong data being read from bcache device
Date: Thu, 16 Nov 2017 13:31:31 -0700 [thread overview]
Message-ID: <8a3d34b9-c49f-3870-fc7f-d337f7077c32@kernel.dk> (raw)
In-Reply-To: <aa11e8f1-5120-9089-c1ad-43ac5057c029@lyle.org>
On 11/16/2017 12:48 PM, Michael Lyle wrote:
> Hi Campbell & Pavel---
>
> On 11/16/2017 11:36 AM, Campbell Steven wrote:
>> On 16 November 2017 at 21:28, Pavel Goran <via-bcache@pvgoran.name> wrote:
>>> Hello list,
>>>
>>> I encountered a severe problem when trying to switch to kernel version 4.14.
>>> In short, reads from the bcache device produce different data in 4.14 and
>>> 4.13.
>
> Thanks for the report. I've heard about this once on the #bcache IRC
> channel too, so it seems this is a real problem, though I've not
> encountered it in my testing yet.
>
> This is just a note to let you all know that I'm looking at this and
> will be seeking a clean repro that's not too painful to bisect to
> determine what's going on.
>
> Most of the 4.14 work predates my involvement on bcache, so I'm coming
> up to speed on it. That said, it looks pretty boring/safe within
> bcache--- and where there's functional change it's almost all in the
> write path which wouldn't be relevant here. So I'm somewhat fearful
> that there is an interaction with something else within the block layer.
The 4.14 block layer changes were pretty boring and uneventful, so that'd
be surprising as well.
I'd suggest just doing a bisect between 4.13 and 4.14, sounds like the
issue is trivially reproducible.
--
Jens Axboe
next prev parent reply other threads:[~2017-11-16 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1321800569.20171116152838@pvgoran.name>
[not found] ` <CAPerZE-KiYVWXtBsu+SR0wCgbSJgzZAufm+3NYdoybjq+6ySbQ@mail.gmail.com>
2017-11-16 19:48 ` Regression in 4.14: wrong data being read from bcache device Michael Lyle
2017-11-16 20:31 ` Jens Axboe [this message]
2017-11-16 23:02 ` Michael Lyle
2017-11-17 3:07 ` Michael Lyle
2017-11-17 15:08 ` Christoph Hellwig
2017-11-17 17:04 ` Michael Lyle
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=8a3d34b9-c49f-3870-fc7f-d337f7077c32@kernel.dk \
--to=axboe@kernel.dk \
--cc=casteven@gmail.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=via-bcache@pvgoran.name \
/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).