From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] usb: hcd: Bump local buffer size in rh_string()
Date: Fri, 17 Jan 2025 15:42:27 +0200 [thread overview]
Message-ID: <Z4peQ4AhE7JzuSFX@smile.fi.intel.com> (raw)
In-Reply-To: <2025011714-catalyst-aide-418b@gregkh>
On Fri, Jan 17, 2025 at 07:11:46AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 16, 2025 at 06:05:43PM +0200, Andy Shevchenko wrote:
> > GCC is not happy about the buffer size:
> >
> > drivers/usb/core/hcd.c:441:48: error: ‘%s’ directive output may be truncated writing up to 64 bytes into a region of size between 35 and 99 [-Werror=format-truncation=]
> > 441 | snprintf (buf, sizeof buf, "%s %s %s", init_utsname()->sysname,
> > | ^~
> > 442 | init_utsname()->release, hcd->driver->description);
> > | ~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Bump the size to get it enough for the possible strings.
...
> > static unsigned
> > rh_string(int id, struct usb_hcd const *hcd, u8 *data, unsigned len)
> > {
> > - char buf[100];
> > + char buf[160];
> > char const *s;
> > static char const langids[4] = {4, USB_DT_STRING, 0x09, 0x04};
>
> Worst case it's properly truncated so why do we need to worry about this
> "warning"?
With CONFIG_WERROR=y it's a compilation error. My goal is to have
i386_defconfig and x86_64_defconfig to be compiled with `make W=1`.
> And what compiler version is giving that, I don't see that
> here in my build testing.
`make W=1` (and be sure that CONFIG_WERROR=y).
$ gcc --version
gcc (Debian 14.2.0-12) 14.2.0
(IIRC that had been started with any GCC from v13?)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-01-17 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 16:05 [PATCH v1 1/1] usb: hcd: Bump local buffer size in rh_string() Andy Shevchenko
2025-01-17 6:11 ` Greg Kroah-Hartman
2025-01-17 13:42 ` Andy Shevchenko [this message]
2025-01-17 14:26 ` Greg Kroah-Hartman
2025-01-17 14:33 ` Andy Shevchenko
2025-01-17 14:46 ` Greg Kroah-Hartman
2025-01-17 19:52 ` 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=Z4peQ4AhE7JzuSFX@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 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).