From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>
Cc: linux-block@vger.kernel.org, hoeppner@linux.ibm.com,
linux-s390@vger.kernel.org, heiko.carstens@de.ibm.com,
gor@linux.ibm.com, borntraeger@de.ibm.com
Subject: Re: [PATCH 0/1] s390/dasd: fix data corruption
Date: Thu, 12 Mar 2020 07:25:07 -0600 [thread overview]
Message-ID: <cd6a5017-7db4-3d66-c58d-40d8b0fda61c@kernel.dk> (raw)
In-Reply-To: <20200312131715.72621-1-sth@linux.ibm.com>
On 3/12/20 7:17 AM, Stefan Haberland wrote:
> Hi Jens,
>
> please find following patch that fixes a likely data corruption when using
> devices with thin provisioning support.
> As this is a severe issue I hope this will make it into RC6. If not, please
> let me know.
Applied for 5.6, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-03-12 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 13:17 [PATCH 0/1] s390/dasd: fix data corruption Stefan Haberland
2020-03-12 13:17 ` [PATCH 1/1] s390/dasd: fix data corruption for thin provisioned devices Stefan Haberland
2020-03-12 13:25 ` Jens Axboe [this message]
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=cd6a5017-7db4-3d66-c58d-40d8b0fda61c@kernel.dk \
--to=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@linux.ibm.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