From: Guenter Roeck <linux@roeck-us.net>
To: Nathan Chancellor <nathan@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Jian Cai <jiancai@google.com>,
Christopher Di Bella <cjdb@google.com>,
Manoj Gupta <manojgupta@google.com>,
Luis Lozano <llozano@google.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] block: Disable -Walign-mismatch for blk-mq.c
Date: Thu, 8 Apr 2021 12:52:45 -0700 [thread overview]
Message-ID: <e48bdeee-c8d4-7048-5899-0aa3fe7243ac@roeck-us.net> (raw)
In-Reply-To: <20210408194458.501617-1-nathan@kernel.org>
On 4/8/21 12:44 PM, Nathan Chancellor wrote:
> LLVM 13 adds a new warning, -Walign-mismatch, which has an instance in
> blk_mq_complete_send_ipi():
>
> block/blk-mq.c:630:39: warning: passing 8-byte aligned argument to
> 32-byte aligned parameter 2 of 'smp_call_function_single_async' may
> result in an unaligned pointer access [-Walign-mismatch]
> smp_call_function_single_async(cpu, &rq->csd);
> ^
> 1 warning generated.
>
> This is expected after commit 4ccafe032005 ("block: unalign
> call_single_data in struct request"), which purposefully unaligned the
> structure to save space. Given that there is no real alignment
> requirement and there have been no reports of issues since that change,
> it should be safe to disable the warning for this one translation unit.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/1328
> Link: https://lore.kernel.org/r/20210310182307.zzcbi5w5jrmveld4@archlinux-ax161/
> Link: https://lore.kernel.org/r/20210330230249.709221-1-jiancai@google.com/
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> block/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block/Makefile b/block/Makefile
> index 8d841f5f986f..d69ac0bd8e61 100644
> --- a/block/Makefile
> +++ b/block/Makefile
> @@ -10,6 +10,7 @@ obj-$(CONFIG_BLOCK) := bio.o elevator.o blk-core.o blk-sysfs.o \
> blk-mq-sysfs.o blk-mq-cpumap.o blk-mq-sched.o ioctl.o \
> genhd.o ioprio.o badblocks.o partitions/ blk-rq-qos.o
>
> +CFLAGS_blk-mq.o := $(call cc-disable-warning, align-mismatch)
> obj-$(CONFIG_BOUNCE) += bounce.o
> obj-$(CONFIG_BLK_SCSI_REQUEST) += scsi_ioctl.o
> obj-$(CONFIG_BLK_DEV_BSG) += bsg.o
>
> base-commit: e49d033bddf5b565044e2abe4241353959bc9120
>
next prev parent reply other threads:[~2021-04-08 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 23:02 [PATCH] blk-mq: fix alignment mismatch Jian Cai
2021-03-30 23:12 ` Guenter Roeck
2021-03-30 23:29 ` Nathan Chancellor
2021-03-31 0:26 ` Guenter Roeck
2021-03-31 1:31 ` Jian Cai
2021-03-31 21:27 ` Jian Cai
2021-03-31 21:58 ` Nathan Chancellor
2021-03-31 22:06 ` Nick Desaulniers
2021-04-08 17:57 ` Jian Cai
2021-04-08 18:12 ` Nathan Chancellor
2021-04-08 18:42 ` Jian Cai
2021-04-08 19:44 ` [PATCH] block: Disable -Walign-mismatch for blk-mq.c Nathan Chancellor
2021-04-08 19:52 ` Guenter Roeck [this message]
2021-03-31 10:38 ` [PATCH] blk-mq: fix alignment mismatch David Laight
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=e48bdeee-c8d4-7048-5899-0aa3fe7243ac@roeck-us.net \
--to=linux@roeck-us.net \
--cc=axboe@kernel.dk \
--cc=cjdb@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=jiancai@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llozano@google.com \
--cc=manojgupta@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®