From: Bjorn Helgaas <helgaas@kernel.org>
To: xujiahao <xujiahao@cmss.chinamobile.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Shijith Thotton <sthotton@marvell.com>,
Vamsi Attunuru <vattunuru@marvell.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] PCI: octep: size the interrupt name buffer for the full format range
Date: Thu, 5 Nov 2026 13:28:06 -0600 [thread overview]
Message-ID: <20261105192806.GA1551537@bhelgaas> (raw)
In-Reply-To: <20261105092705.3099201-1-xujiahao@cmss.chinamobile.com>
On Thu, Nov 05, 2026 at 05:27:04PM +0800, xujiahao wrote:
> octep_hp_request_irq() formats the interrupt name with "octep_hp_%d"
> into a 16-byte array. The prefix is 9 bytes and a full-range %d
> argument can add up to 11 more, so the worst case needs 21 bytes
> including the terminator and 0-day reports:
>
> drivers/pci/hotplug/octep_hp.c:312:53: warning: '%d' directive output
> may be truncated writing between 1 and 10 bytes into a region of size 7
> [-Wformat-truncation=]
> note: 'snprintf' output between 11 and 20 bytes into a destination of
> size 16
Thanks for including the warning text. To make the git log more
searchable, please keep the lines intact even though they are pretty
long.
Also run "git log --oneline drivers/pci/hotplug/" and match the
capitalization style.
> The values passed today are OCTEP_HP_INTR_ENA and OCTEP_HP_INTR_DIS, so
OCTEP_HP_INTR_ENA (0) and OCTEP_HP_INTR_DIS (1)
> no truncation actually happens, but the buffer carries no margin over
> the format's worst case. Give it the room so the warning stops coming
> back from builds that cannot narrow the argument.
prev parent reply other threads:[~2026-11-05 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 9:27 xujiahao
2026-11-05 19:28 ` Bjorn Helgaas [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=20261105192806.GA1551537@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sthotton@marvell.com \
--cc=vattunuru@marvell.com \
--cc=xujiahao@cmss.chinamobile.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
all inboxes | Powered by JetHome®