From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: dwc: Fix potential truncation in dw_pcie_edma_irq_verify()
Date: Sat, 4 Jan 2025 14:16:52 +0530 [thread overview]
Message-ID: <20250104084652.2t6oilbns7kfz2ep@thinkpad> (raw)
In-Reply-To: <Z3i8fQ8CRGzZuhUT@ryzen>
On Sat, Jan 04, 2025 at 05:43:41AM +0100, Niklas Cassel wrote:
> On Sat, Jan 04, 2025 at 09:59:01AM +0530, Manivannan Sadhasivam wrote:
> > On Sat, Jan 04, 2025 at 01:21:20AM +0100, Niklas Cassel wrote:
> > > Increase the size of the string buffer to avoid potential truncation in
> > > dw_pcie_edma_irq_verify().
> > >
> > > This fixes the following build warning when compiling with W=1:
> > >
> > > drivers/pci/controller/dwc/pcie-designware.c: In function ‘dw_pcie_edma_detect’:
> > > drivers/pci/controller/dwc/pcie-designware.c:989:50: warning: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into a region of size 3 [-Wformat-truncation=]
> > > 989 | snprintf(name, sizeof(name), "dma%d", pci->edma.nr_irqs);
> > > | ^~
> > >
> > > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> > > ---
> > > Changes since v2:
> > > -Simply increase the size of the string buffer instead of chaning the
> > > print format specifier.
> > >
> > > drivers/pci/controller/dwc/pcie-designware.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
> > > index 3c683b6119c3..145e7f579072 100644
> > > --- a/drivers/pci/controller/dwc/pcie-designware.c
> > > +++ b/drivers/pci/controller/dwc/pcie-designware.c
> > > @@ -971,7 +971,7 @@ static int dw_pcie_edma_irq_verify(struct dw_pcie *pci)
> > > {
> > > struct platform_device *pdev = to_platform_device(pci->dev);
> > > u16 ch_cnt = pci->edma.ll_wr_cnt + pci->edma.ll_rd_cnt;
> > > - char name[6];
> > > + char name[15];
> >
> > Isn't 14 big enough to hold INT_MAX + 'dma'? Not a big deal, but asking just for
> > the sake of correctness.
>
> We need to be able to hold INT_MIN which is "-2147483648" 11 chars/bytes
> + "dma" 3 chars/bytes + terminating null byte (1 char/byte) = 15.
>
Ah, brain fade (missing the null byte termination).
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-01-04 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 0:21 [PATCH v3] PCI: dwc: Fix potential truncation in dw_pcie_edma_irq_verify() Niklas Cassel
2025-01-04 4:29 ` Manivannan Sadhasivam
2025-01-04 4:43 ` Niklas Cassel
2025-01-04 8:46 ` Manivannan Sadhasivam [this message]
2025-01-15 11:24 ` Krzysztof Wilczyński
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=20250104084652.2t6oilbns7kfz2ep@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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