From: Vitaly Chikunov <vt@altlinux.org>
To: "Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
KY 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>,
Jakub Kicinski <kuba@kernel.org>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Long Li <longli@microsoft.com>
Subject: Re: [PATCH v3] drivers: hv: vmbus: Fix build on Clang 12 failed by DMA_BIT_MASK(64) expansion
Date: Sat, 5 Feb 2022 11:06:14 +0300 [thread overview]
Message-ID: <20220205080614.52gu4mtjli4h2m3c@altlinux.org> (raw)
In-Reply-To: <20220205040552.fnshfhin3fij67t6@altlinux.org>
On Sat, Feb 05, 2022 at 07:05:53AM +0300, Vitaly Chikunov wrote:
> On Fri, Feb 04, 2022 at 04:10:49PM +0000, Michael Kelley (LINUX) wrote:
> > From: Vitaly Chikunov <vt@altlinux.org> Sent: Friday, February 4, 2022 5:05 AM
> > >
> > > 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:
> > >
> > > 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.
> > >
> > > 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>
> > > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> > > ---
> > > drivers/hv/vmbus_drv.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> > > index 17bf55fe3169..a1306ca15d3f 100644
> > > --- a/drivers/hv/vmbus_drv.c
> > > +++ b/drivers/hv/vmbus_drv.c
> > > @@ -2079,7 +2079,8 @@ struct hv_device *vmbus_device_create(const guid_t *type,
> > > return child_device_obj;
> > > }
> > >
> > > -static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
> > > +/* 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
> > > */
> > > --
> > > 2.33.0
> >
> > Instead of the hack approach, does the following code rearrangement solve
> > the problem by eliminating the use of DMA_BIT_MASK(64) in a static initializer?
> > I don't have Clang handy to try it.
>
> Yes this compiles well on Clang.
How to reproduce in Docker (as in 'totally non-secure'):
kernel-src$ make mrproper
kernel-src$ docker run --rm -it -v $PWD:/src -w /src kernelci/clang-12
in-docker# make CC=clang LLVM=1 O=/tmp/k allyesconfig drivers/hv/
`make mrproper` is required for `O=`, where `O=` is to not pollute
kernel tree (which will be rw bind mounted into /src) with root owned
files (since Docker runs under real root by default), `allyesconfig` is
to enable `HYPERV=y` the easy way. There are also other clang versions up
to clang-14 (they all fail with that global DMA_BIT_MASK(64) error).
Instead of `-v $PWD:/src -w /src` options to docker you can do git clone
inside, this is perhaps will be slightly more secure, and you don't need
to mrproper your tree (which will destroy .config).
Vitaly,
>
> Vitaly,
>
> >
> > This approach also more closely follows the pattern used in other device types.
> >
> > Michael
> >
> >
> > diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> > index 17bf55f..0d96634 100644
> > --- a/drivers/hv/vmbus_drv.c
> > +++ b/drivers/hv/vmbus_drv.c
> > @@ -2079,7 +2079,6 @@ struct hv_device *vmbus_device_create(const guid_t *type,
> > return child_device_obj;
> > }
> >
> > -static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
> > /*
> > * vmbus_device_register - Register the child device
> > */
> > @@ -2120,8 +2119,9 @@ int vmbus_device_register(struct hv_device *child_device_obj)
> > }
> > hv_debug_add_dev_dir(child_device_obj);
> >
> > - child_device_obj->device.dma_mask = &vmbus_dma_mask;
> > child_device_obj->device.dma_parms = &child_device_obj->dma_parms;
> > + child_device_obj->device.dma_mask = &child_device_obj->dma_mask;
> > + dma_set_mask(&child_device_obj->device, DMA_BIT_MASK(64));
> > return 0;
> >
> > err_kset_unregister:
> > diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
> > index f565a89..fe2e017 100644
> > --- a/include/linux/hyperv.h
> > +++ b/include/linux/hyperv.h
> > @@ -1262,6 +1262,7 @@ struct hv_device {
> > struct vmbus_channel *channel;
> > struct kset *channels_kset;
> > struct device_dma_parameters dma_parms;
> > + u64 dma_mask;
> >
> > /* place holder to keep track of the dir for hv device in debugfs */
> > struct dentry *debug_dir;
next prev parent reply other threads:[~2022-02-05 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:05 [PATCH v3] drivers: hv: vmbus: Fix build on Clang 12 failed by DMA_BIT_MASK(64) expansion Vitaly Chikunov
2022-02-04 16:10 ` Michael Kelley (LINUX)
2022-02-05 4:05 ` Vitaly Chikunov
2022-02-05 8:06 ` Vitaly Chikunov [this message]
2022-02-05 14:41 ` Michael Kelley (LINUX)
2022-02-06 1:02 ` Vitaly Chikunov
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=20220205080614.52gu4mtjli4h2m3c@altlinux.org \
--to=vt@altlinux.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@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