From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mikulas Patocka <mpatocka@redhat.com>
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: Mon, 26 Aug 2024 10:08:41 +0200 (CEST) [thread overview]
Message-ID: <512a07c-d41a-27c4-b1f9-8fe19352d1f@linux-m68k.org> (raw)
In-Reply-To: <c994d5e-cc3d-d7f5-ce3-fd2cf91e850@redhat.com>
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')) {
^
I could reproduce the issue with gcc-5(Ubuntu 5.5.0-12ubuntu1) on x86 .
The condition indeed looks hard to read. Perhaps it should be rewritten as
"le32_to_cpu(ic->sb->journal_sections) == (ic->mode == 'I')"?
> r = -EINVAL;
> - ti->error = "Corrupted superblock, journal_sections is 0";
> + if (ic->mode != 'I')
> + ti->error = "Corrupted superblock, journal_sections is 0";
> + else
> + ti->error = "Corrupted superblock, journal_sections is not 0";
> goto bad;
> }
> /* make sure that ti->max_io_len doesn't overflow */
[1] https://lore.kernel.org/20240729092807.2235937-1-geert@linux-m68k.org
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2024-08-26 8:08 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 [this message]
2024-09-03 10:15 ` Mikulas Patocka
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=512a07c-d41a-27c4-b1f9-8fe19352d1f@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=dm-devel@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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®