From: Christoph Hellwig <hch@lst.de>
To: axboe@kernel.dk
Cc: mpatocka@redhat.com, gmazyland@gmail.com,
martin.petersen@oracle.com, linux-block@vger.kernel.org,
dm-devel@redhat.com
Subject: integrity regression fixes for 4.13-rc
Date: Wed, 9 Aug 2017 17:47:25 +0200 [thread overview]
Message-ID: <20170809154727.2085-1-hch@lst.de> (raw)
Hi Jens,
this series fixes regressions in the integrity handling update in 4.13-rc.
The first one was sent earlier by Milan and while both Martin and I aren't
exactly happy about the way dm uses the integrity code to cause this
regression this minimal fix gets us back to the status quo.
The second one makes sure that we only verify the DIF checksums on the
lowest layer where we attach the integrity information.
next reply other threads:[~2017-08-09 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 15:47 Christoph Hellwig [this message]
2017-08-09 15:47 ` [PATCH 1/2] bio-integrity: Fix regression if profile verify_fn is NULL Christoph Hellwig
2017-08-09 15:47 ` [PATCH 2/2] bio-integrity: only verify integrity on the lowest stacked driver Christoph Hellwig
2017-08-09 15:59 ` integrity regression fixes for 4.13-rc Jens Axboe
2017-08-09 16:21 ` Martin K. Petersen
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=20170809154727.2085-1-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.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