From: Sasha Levin <sashal@kernel.org>
To: Jack Wang <jinpuwang@gmail.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [stable-4.14 0/2] block layer fixes for silent data corruption
Date: Tue, 25 Jun 2019 15:50:38 -0400 [thread overview]
Message-ID: <20190625195038.GB7898@sasha-vm> (raw)
In-Reply-To: <20190625141725.26220-1-jinpuwang@gmail.com>
On Tue, Jun 25, 2019 at 04:17:23PM +0200, Jack Wang wrote:
>A silent data corruption was introduced in v4.10-rc1 with commit
>72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
>with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects
>users of O_DIRECT, in our case a KVM virtual machine with drives
>which use qemu's "cache=none" option.
>
>The other 2 commits has been accepted in 4.14, but 2 are missing,
>ref: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796542
>
>Please consider to include them in next release.
I've ended up cherry picking these two into the 4.14 tree.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-25 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:17 [stable-4.14 0/2] block layer fixes for silent data corruption Jack Wang
2019-06-25 14:17 ` [stable-4.14 1/2] block: add a lower-level bio_add_page interface Jack Wang
2019-06-25 14:24 ` Christoph Hellwig
2019-06-25 14:27 ` Jinpu Wang
2019-06-25 14:33 ` Christoph Hellwig
2019-06-25 14:39 ` Jinpu Wang
2019-06-25 14:17 ` [stable-4.14 2/2] block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs Jack Wang
2019-06-25 19:50 ` Sasha Levin [this message]
2019-06-26 10:01 ` [stable-4.14 0/2] block layer fixes for silent data corruption Jinpu Wang
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=20190625195038.GB7898@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jinpuwang@gmail.com \
--cc=stable@vger.kernel.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 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.