public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: kernel test robot <lkp@intel.com>,
	Krishna Kurapati <quic_kriskura@quicinc.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-usb@vger.kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	Johan Hovold <johan+linaro@kernel.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Subject: Re: [usb:usb-testing 7/12] drivers/usb/dwc3/core.c:1482:69: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size 4
Date: Wed, 24 Apr 2024 08:41:56 +0200	[thread overview]
Message-ID: <ZiiptMEL2_AdBsJA@hovoldconsulting.com> (raw)
In-Reply-To: <202404241215.Mib19Cu7-lkp@intel.com>

On Wed, Apr 24, 2024 at 01:03:07PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> head:   a160e1202ca318a85c70cf5831f172cc79a24c57
> commit: 846b4bacf2d48212f271fc1ef7488bcdf2c75bcb [7/12] usb: dwc3: core: Refactor PHY logic to support Multiport Controller
> config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20240424/202404241215.Mib19Cu7-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240424/202404241215.Mib19Cu7-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202404241215.Mib19Cu7-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    drivers/usb/dwc3/core.c: In function 'dwc3_core_get_phy':
> >> drivers/usb/dwc3/core.c:1482:69: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size 4 [-Wformat-truncation=]
>     1482 |                         snprintf(phy_name, sizeof(phy_name),  "usb2-%d", i);
>          |                                                                     ^~
>    drivers/usb/dwc3/core.c:1482:63: note: directive argument in the range [-2147483641, 254]
>     1482 |                         snprintf(phy_name, sizeof(phy_name),  "usb2-%d", i);

This version or s390-build of gcc appears to be confused as the
variable i is clearly in the range [0,254] in these for loops.

I also don't see this W=1 warning with my gcc-10 (aarch64).

It may be possible to work around this by using u8 type for the iterator
(and %u in the format), but I'm not sure we should be working around
compiler bugs like that.

>          |                                                               ^~~~~~~~~
>    drivers/usb/dwc3/core.c:1482:25: note: 'snprintf' output between 7 and 17 bytes into a destination of size 9
>     1482 |                         snprintf(phy_name, sizeof(phy_name),  "usb2-%d", i);
>          |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>   1446	static int dwc3_core_get_phy(struct dwc3 *dwc)
>   1447	{

>   1450		char phy_name[9];
>   1451		int ret;
>   1452		int i;

>   1478		for (i = 0; i < dwc->num_usb2_ports; i++) {
>   1479			if (dwc->num_usb2_ports == 1)
>   1480				snprintf(phy_name, sizeof(phy_name), "usb2-phy");
>   1481			else
> > 1482				snprintf(phy_name, sizeof(phy_name),  "usb2-%d", i);

>   1493		}

Johan

  reply	other threads:[~2024-04-24  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  5:03 [usb:usb-testing 7/12] drivers/usb/dwc3/core.c:1482:69: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size 4 kernel test robot
2024-04-24  6:41 ` Johan Hovold [this message]
2024-04-25  5:08   ` Krishna Kurapati PSSNV
2024-04-25 15:18     ` Greg Kroah-Hartman

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=ZiiptMEL2_AdBsJA@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=andersson@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan+linaro@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quic_kriskura@quicinc.com \
    /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