From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Zhu Yanjun <yanjun.zhu@linux.dev>,
Zhu Yanjun <yanjun.zhu@intel.com>,
jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, virtualization@lists.linux.dev,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] virtio_net: Fix "‘%d’ directive writing between 1 and 11 bytes into a region of size 10" warnings
Date: Tue, 26 Dec 2023 13:11:18 -0500 [thread overview]
Message-ID: <20231226130707-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231226100113.4ea54838@hermes.local>
On Tue, Dec 26, 2023 at 10:01:13AM -0800, Stephen Hemminger wrote:
> On Tue, 26 Dec 2023 19:53:58 +0800
> Zhu Yanjun <yanjun.zhu@linux.dev> wrote:
>
> > The warnings are as below:
> >
> > "
> >
> > drivers/net/virtio_net.c: In function ‘init_vqs’:
> > drivers/net/virtio_net.c:4551:48: warning: ‘%d’ directive writing
> > between 1 and 11 bytes into a region of size 10 [-Wformat-overflow=]
> > 4551 | sprintf(vi->rq[i].name, "input.%d", i);
> > | ^~
> > In function ‘virtnet_find_vqs’,
> > inlined from ‘init_vqs’ at drivers/net/virtio_net.c:4645:8:
> > drivers/net/virtio_net.c:4551:41: note: directive argument in the range
> > [-2147483643, 65534]
> > 4551 | sprintf(vi->rq[i].name, "input.%d", i);
> > | ^~~~~~~~~~
> > drivers/net/virtio_net.c:4551:17: note: ‘sprintf’ output between 8 and
> > 18 bytes into a destination of size 16
> > 4551 | sprintf(vi->rq[i].name, "input.%d", i);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > drivers/net/virtio_net.c: In function ‘init_vqs’:
> > drivers/net/virtio_net.c:4552:49: warning: ‘%d’ directive writing
> > between 1 and 11 bytes into a region of size 9 [-Wformat-overflow=]
> > 4552 | sprintf(vi->sq[i].name, "output.%d", i);
> > | ^~
> > In function ‘virtnet_find_vqs’,
> > inlined from ‘init_vqs’ at drivers/net/virtio_net.c:4645:8:
> > drivers/net/virtio_net.c:4552:41: note: directive argument in the range
> > [-2147483643, 65534]
> > 4552 | sprintf(vi->sq[i].name, "output.%d", i);
> > | ^~~~~~~~~~~
> > drivers/net/virtio_net.c:4552:17: note: ‘sprintf’ output between 9 and
> > 19 bytes into a destination of size 16
> > 4552 | sprintf(vi->sq[i].name, "output.%d", i);
> >
> > "
> >
> > Please review.
> >
> > Best Regards,
> >
> > Zhu Yanjun
> >
> > 在 2023/12/26 19:45, Zhu Yanjun 写道:
> > > From: Zhu Yanjun <yanjun.zhu@linux.dev>
> > >
> > > Fix a warning when building virtio_net driver.
> > >
> > > Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
> > > ---
> > > drivers/net/virtio_net.c | 5 +++--
> > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > > index 49625638ad43..cf57eddf768a 100644
> > > --- a/drivers/net/virtio_net.c
> > > +++ b/drivers/net/virtio_net.c
> > > @@ -4508,10 +4508,11 @@ static int virtnet_find_vqs(struct virtnet_info *vi)
> > > {
> > > vq_callback_t **callbacks;
> > > struct virtqueue **vqs;
> > > - int ret = -ENOMEM;
> > > - int i, total_vqs;
> > > const char **names;
> > > + int ret = -ENOMEM;
> > > + int total_vqs;
> > > bool *ctx;
> > > + u16 i;
> > >
> > > /* We expect 1 RX virtqueue followed by 1 TX virtqueue, followed by
> > > * possible N-1 RX/TX queue pairs used in multiqueue mode, followed by
> >
>
> If you change the variable type to u16, then the format string should no
> longer use %d. Instead should be %u
I would just use unsigned FWIW. But it doesn't matter the range is
limited here. It's just that the compiler can't figure it out.
--
MST
prev parent reply other threads:[~2023-12-26 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 11:45 [PATCH 1/1] virtio_net: Fix "‘%d’ directive writing between 1 and 11 bytes into a region of size 10" warnings Zhu Yanjun
2023-12-26 11:53 ` Zhu Yanjun
2023-12-26 12:43 ` Xuan Zhuo
2023-12-26 18:01 ` Stephen Hemminger
2023-12-26 18:11 ` Michael S. Tsirkin [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=20231226130707-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yanjun.zhu@intel.com \
--cc=yanjun.zhu@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).