From: Mikulas Patocka <mpatocka@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mike Snitzer <snitzer@kernel.org>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/2] dm-integrity: introduce the Inline mode
Date: Tue, 3 Sep 2024 12:15:28 +0200 (CEST) [thread overview]
Message-ID: <46e7758b-c9d1-d381-3959-16cb943e5de5@redhat.com> (raw)
In-Reply-To: <512a07c-d41a-27c4-b1f9-8fe19352d1f@linux-m68k.org>
On Mon, 26 Aug 2024, Geert Uytterhoeven wrote:
> Hi Mikulas,
>
> On Tue, 25 Jun 2024, Mikulas Patocka wrote:
> > This commit introduces a new 'I' mode for dm-integrity.
> >
> > The 'I' mode may be selected if the underlying device has non-power-of-2
> > sector size. In this mode, dm-integrity will store integrity data
> > directly in device's sectors and it will not use journal.
> >
> > This mode improves performance and reduces flash wear because there would
> > be no journal writes.
> >
> > Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> Thanks for your patch, which is now commit fb0987682c629c1d
> ("dm-integrity: introduce the Inline mode") in v6.11-rc1.
>
> > @@ -4433,9 +4737,12 @@ static int dm_integrity_ctr(struct dm_ta
> > ti->error = "Block size doesn't match the information in
> > superblock";
> > goto bad;
> > }
> > - if (!le32_to_cpu(ic->sb->journal_sections)) {
> > + if (!le32_to_cpu(ic->sb->journal_sections) != (ic->mode == 'I')) {
>
> As reporting before in e.g. [1], this is causing build failures with
> gcc-5 and -Werror:
>
> drivers/md/dm-integrity.c:4718:52: error: logical not is only applied to
> the left hand side of comparison [-Werror=logical-not-parentheses]
> if (!le32_to_cpu(ic->sb->journal_sections) != (ic->mode == 'I')) {
Hi
I fixed it. The fix will be submitted upstream in the next merge window.
Mikulas
prev parent reply other threads:[~2024-09-03 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c994d5e-cc3d-d7f5-ce3-fd2cf91e850@redhat.com>
2024-08-26 8:08 ` Geert Uytterhoeven
2024-09-03 10:15 ` Mikulas Patocka [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=46e7758b-c9d1-d381-3959-16cb943e5de5@redhat.com \
--to=mpatocka@redhat.com \
--cc=arnd@arndb.de \
--cc=dm-devel@lists.linux.dev \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®