From: Stephen Hemminger <stephen@networkplumber.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Jakub Kicinski' <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] drivers: net: sky2: Fix -Wstringop-truncation with W=1
Date: Tue, 3 Nov 2020 08:26:51 -0800 [thread overview]
Message-ID: <20201103082651.7edadae6@hermes.local> (raw)
In-Reply-To: <20201103082501.39eac063@hermes.local>
On Tue, 3 Nov 2020 08:25:01 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> On Tue, 3 Nov 2020 10:19:55 +0000
> David Laight <David.Laight@ACULAB.COM> wrote:
>
> > From: Jakub Kicinski
> > > Sent: 03 November 2020 00:01
> > >
> > > On Sat, 31 Oct 2020 18:40:28 +0100 Andrew Lunn wrote:
> > > > In function ‘strncpy’,
> > > > inlined from ‘sky2_name’ at drivers/net/ethernet/marvell/sky2.c:4903:3,
> > > > inlined from ‘sky2_probe’ at drivers/net/ethernet/marvell/sky2.c:5049:2:
> > > > ./include/linux/string.h:297:30: warning: ‘__builtin_strncpy’ specified bound 16 equals destination
> > > size [-Wstringop-truncation]
> > > >
> > > > None of the device names are 16 characters long, so it was never an
> > > > issue, but reduce the length of the buffer size by one to avoid the
> > > > warning.
> > > >
> > > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > > > ---
> > > > drivers/net/ethernet/marvell/sky2.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/net/ethernet/marvell/sky2.c b/drivers/net/ethernet/marvell/sky2.c
> > > > index 25981a7a43b5..35b0ec5afe13 100644
> > > > --- a/drivers/net/ethernet/marvell/sky2.c
> > > > +++ b/drivers/net/ethernet/marvell/sky2.c
> > > > @@ -4900,7 +4900,7 @@ static const char *sky2_name(u8 chipid, char *buf, int sz)
> > > > };
> > > >
> > > > if (chipid >= CHIP_ID_YUKON_XL && chipid <= CHIP_ID_YUKON_OP_2)
> > > > - strncpy(buf, name[chipid - CHIP_ID_YUKON_XL], sz);
> > > > + strncpy(buf, name[chipid - CHIP_ID_YUKON_XL], sz - 1);
> > >
> > > Hm. This irks the eye a little. AFAIK the idiomatic code would be:
> > >
> > > strncpy(buf, name..., sz - 1);
> > > buf[sz - 1] = '\0';
> > >
> > > Perhaps it's easier to convert to strscpy()/strscpy_pad()?
> > >
> > > > else
> > > > snprintf(buf, sz, "(chip %#x)", chipid);
> > > > return buf;
> >
> > Is the pad needed?
> > It isn't present in the 'else' branch.
>
> Since this is non-critical code and is only ther to print something useful
> on boot, why not just use snprintf on both sides of statement?
Like this is what I meant...
diff --git a/drivers/net/ethernet/marvell/sky2.c b/drivers/net/ethernet/marvell/sky2.c
index 25981a7a43b5..ebe1406c6e64 100644
--- a/drivers/net/ethernet/marvell/sky2.c
+++ b/drivers/net/ethernet/marvell/sky2.c
@@ -4900,7 +4900,7 @@ static const char *sky2_name(u8 chipid, char *buf, int sz)
};
if (chipid >= CHIP_ID_YUKON_XL && chipid <= CHIP_ID_YUKON_OP_2)
- strncpy(buf, name[chipid - CHIP_ID_YUKON_XL], sz);
+ snprintf(buf, sz, "%s", name[chipid - CHIP_ID_YUKON_XL]);
else
snprintf(buf, sz, "(chip %#x)", chipid);
return buf;
prev parent reply other threads:[~2020-11-03 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 17:40 [PATCH net-next] drivers: net: sky2: Fix -Wstringop-truncation with W=1 Andrew Lunn
2020-11-03 0:01 ` Jakub Kicinski
2020-11-03 10:19 ` David Laight
2020-11-03 16:25 ` Stephen Hemminger
2020-11-03 16:26 ` Stephen Hemminger [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=20201103082651.7edadae6@hermes.local \
--to=stephen@networkplumber.org \
--cc=David.Laight@ACULAB.COM \
--cc=andrew@lunn.ch \
--cc=kuba@kernel.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.