From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] misc: pci_endpoint_test: Fix potential truncation in pci_endpoint_test_probe()
Date: Fri, 14 Feb 2025 23:12:45 +0530 [thread overview]
Message-ID: <20250214174245.ctrzbp7bcd5v4xdt@thinkpad> (raw)
In-Reply-To: <20250123103127.3581432-2-cassel@kernel.org>
On Thu, Jan 23, 2025 at 11:31:28AM +0100, Niklas Cassel wrote:
> Increase the size of the string buffer to avoid potential truncation in
> pci_endpoint_test_probe().
>
> This fixes the following build warning when compiling with W=1:
>
> drivers/misc/pci_endpoint_test.c:29:49: note: directive argument in the range [0, 2147483647]
> 29 | #define DRV_MODULE_NAME "pci-endpoint-test"
> | ^~~~~~~~~~~~~~~~~~~
> drivers/misc/pci_endpoint_test.c:998:38: note: in expansion of macro ‘DRV_MODULE_NAME’
> 998 | snprintf(name, sizeof(name), DRV_MODULE_NAME ".%d", id);
> | ^~~~~~~~~~~~~~~
> drivers/misc/pci_endpoint_test.c:998:9: note: ‘snprintf’ output between 20 and 29 bytes into a destination of size 24
> 998 | snprintf(name, sizeof(name), DRV_MODULE_NAME ".%d", id);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
Applied to pci/endpoint!
- Mani
> ---
> drivers/misc/pci_endpoint_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
> index 8e48a15100f1..b0db94161d31 100644
> --- a/drivers/misc/pci_endpoint_test.c
> +++ b/drivers/misc/pci_endpoint_test.c
> @@ -912,7 +912,7 @@ static int pci_endpoint_test_probe(struct pci_dev *pdev,
> {
> int ret;
> int id;
> - char name[24];
> + char name[29];
> enum pci_barno bar;
> void __iomem *base;
> struct device *dev = &pdev->dev;
> --
> 2.48.1
>
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2025-02-14 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:31 [PATCH] misc: pci_endpoint_test: Fix potential truncation in pci_endpoint_test_probe() Niklas Cassel
2025-01-23 16:00 ` Frank Li
2025-02-01 15:47 ` Manivannan Sadhasivam
2025-02-13 13:41 ` Niklas Cassel
2025-02-14 17:42 ` Manivannan Sadhasivam [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=20250214174245.ctrzbp7bcd5v4xdt@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=arnd@arndb.de \
--cc=cassel@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@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