From: Milan Broz <gmazyland@gmail.com>
To: "Bruno Prémont" <bonbons@sysophe.eu>,
"Mikulas Patocka" <mpatocka@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm-crypt, dm-integrity: allow unaligned bv_offset
Date: Tue, 7 Nov 2017 09:31:01 +0100 [thread overview]
Message-ID: <f8bb8497-7b6d-3ce1-8a59-0eb90975c4c0@gmail.com> (raw)
In-Reply-To: <20171107091323.20664e3f@pluto.restena.lu>
On 11/07/2017 09:13 AM, Bruno Prémont wrote:
>> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>> Cc: stable@vger.kernel.org # v4.12+
>> Fixes: 8f0009a22517 ("dm crypt: optionally support larger encryption sector size")
>> Fixes: 7eada909bfd7 ("dm: add integrity target")
>
> Reported-by: Bruno Prémont <bonbons@sysophe.eu>
> Tested-by: Bruno Prémont <bonbons@sysophe.eu>
>
> Successfully tested on 4.12.14, 4.13.11 and 4.14-rc8+ (e4880bc5dfb1).
Thanks!
(That alignment check was added after our discussion - we wanted
to have dm-crypt and dm-integrity to check the same thing, just to trigger
possible data corruption, but obviously it was incorrect check.)
It must go to stable well, I think there are possibly more situations
we broke for dm-crypt by this.
Reviewed-by: Milan Broz <gmazyland@gmail.com>
m.
prev parent reply other threads:[~2017-11-07 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 20:39 [Regression, Bisected] dm-crypt IO failures with active slub_debug in 4.12 and later Bruno Prémont
2017-11-06 16:18 ` Mike Snitzer
2017-11-06 22:29 ` Bruno Prémont
2017-11-06 23:57 ` [PATCH] dm-crypt, dm-integrity: allow unaligned bv_offset (was: [Regression, Bisected] dm-crypt IO failures with active slub_debug in 4.12 and later) Mikulas Patocka
2017-11-07 8:13 ` Bruno Prémont
2017-11-07 8:31 ` Milan Broz [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=f8bb8497-7b6d-3ce1-8a59-0eb90975c4c0@gmail.com \
--to=gmazyland@gmail.com \
--cc=bonbons@sysophe.eu \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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
Powered by JetHome