From: Wei Liu <wei.liu@kernel.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Vitaly Chikunov <vt@altlinux.org>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Michael Kelley <mikelley@microsoft.com>,
Long Li <longli@microsoft.com>,
linux-hyperv@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>
Subject: Re: [PATCH v2] drivers: hv: vmbus: Fix build on Clang 12 failed by DMA_BIT_MASK(64) expansion
Date: Fri, 4 Feb 2022 12:05:24 +0000 [thread overview]
Message-ID: <20220204120524.bhnbmfzcgpsrlezv@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <871r0jas2l.fsf@redhat.com>
On Fri, Feb 04, 2022 at 10:39:46AM +0100, Vitaly Kuznetsov wrote:
> Vitaly Chikunov <vt@altlinux.org> writes:
>
> > Clang 12.0.1 cannot understand that value 64 is excluded from the shift
> > at compile time (for use in global context) resulting in build error[1]:
> >
> > drivers/hv/vmbus_drv.c:2082:29: error: shift count >= width of type [-Werror,-Wshift-count-overflow]
> > static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
> > ^~~~~~~~~~~~~~~~
> > ./include/linux/dma-mapping.h:76:54: note: expanded from macro 'DMA_BIT_MASK'
> > #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
> > ^ ~~~
> >
> > Avoid using DMA_BIT_MASK macro for that corner case.
>
> Was this reported to Clang already? It looks like a clear bug on their side.
This is already known.
I dealt with a similar report before. At the time I decided nothing's
wrong with the code.
https://lore.kernel.org/linux-kernel/YcC1CobR%2Fn0tJhdV@archlinux-ax161/
https://github.com/ClangBuiltLinux/linux/issues/92
I can certainly live with a workaround like this.
>
> >
> > Cc: Tianyu Lan <Tianyu.Lan@microsoft.com>
> > Cc: Michael Kelley <mikelley@microsoft.com>
> > Cc: Long Li <longli@microsoft.com>
> > Cc: Wei Liu <wei.liu@kernel.org>
> > Link: https://lore.kernel.org/linux-hyperv/20220203235828.hcsj6najsl7yxmxa@altlinux.org/
> > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> > ---
> > Changes since v1:
> > - Patch description updated, s/GCC 11/Clang 12/.
> >
> > drivers/hv/vmbus_drv.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> > index 17bf55fe3169..2376ee484362 100644
> > --- a/drivers/hv/vmbus_drv.c
> > +++ b/drivers/hv/vmbus_drv.c
> > @@ -2079,7 +2079,7 @@ struct hv_device *vmbus_device_create(const guid_t *type,
> > return child_device_obj;
> > }
> >
> > -static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
Please add a comment here
// Use ~0ULL instead of DMA_BIT_MASK(64) to work around a bug in Clang.
> > +static u64 vmbus_dma_mask = ~0ULL;
> > /*
> > * vmbus_device_register - Register the child device
> > */
>
> --
> Vitaly
>
next prev parent reply other threads:[~2022-02-04 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 2:26 [PATCH v2] drivers: hv: vmbus: Fix build on Clang 12 failed by DMA_BIT_MASK(64) expansion Vitaly Chikunov
2022-02-04 9:39 ` Vitaly Kuznetsov
2022-02-04 12:05 ` Wei Liu [this message]
2022-02-04 12:06 ` Wei Liu
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=20220204120524.bhnbmfzcgpsrlezv@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.com \
--cc=vt@altlinux.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