From: Sohil Mehta <sohil.mehta@intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] x86/callthunks: Fix some potential string truncation in callthunks_debugfs_init()
Date: Tue, 19 Dec 2023 16:32:13 +0530 [thread overview]
Message-ID: <4d4e488d-45d6-4496-b165-c349c67d4f11@intel.com> (raw)
In-Reply-To: <8c2b24df3c077e55b2a4d91a7ffd08fa48e28d0a.1702803679.git.christophe.jaillet@wanadoo.fr>
On 12/17/2023 2:31 PM, Christophe JAILLET wrote:
> When compiled with W=1, we get:
> arch/x86/kernel/callthunks.c: In function ‘callthunks_debugfs_init’:
> arch/x86/kernel/callthunks.c:394:35: error: ‘%lu’ directive writing between 1 and 10 bytes into a region of size 7 [-Werror=format-overflow=]
> 394 | sprintf(name, "cpu%lu", cpu);
> | ^~~
> arch/x86/kernel/callthunks.c:394:31: note: directive argument in the range [0, 4294967294]
> 394 | sprintf(name, "cpu%lu", cpu);
> | ^~~~~~~~
> arch/x86/kernel/callthunks.c:394:17: note: ‘sprintf’ output between 5 and 14 bytes into a destination of size 10
> 394 | sprintf(name, "cpu%lu", cpu);
> |
>
> So, give some more space to 'name' to silence the warning.
It might be useful to specify that "some more space" hasn't been
arbitrarily decided. It took me a few minutes to figure that out.
With the max cpu number being 4294967294 with 10 characters, a total of
14 chars would be enough to print "cpu%lu".
> (and fix the issue should a lucky one have a config with so many
> CPU!)
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> arch/x86/kernel/callthunks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Apart from that, please feel free to add:
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> diff --git a/arch/x86/kernel/callthunks.c b/arch/x86/kernel/callthunks.c
> index cf7e5be1b844..26182a7d12b3 100644
> --- a/arch/x86/kernel/callthunks.c
> +++ b/arch/x86/kernel/callthunks.c
> @@ -388,7 +388,7 @@ static int __init callthunks_debugfs_init(void)
> dir = debugfs_create_dir("callthunks", NULL);
> for_each_possible_cpu(cpu) {
> void *arg = (void *)cpu;
> - char name [10];
> + char name[14];
>
> sprintf(name, "cpu%lu", cpu);
> debugfs_create_file(name, 0644, dir, arg, &dfs_ops);
next prev parent reply other threads:[~2023-12-19 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 9:01 Christophe JAILLET
2023-12-19 11:02 ` Sohil Mehta [this message]
2023-12-19 17:55 ` Christophe JAILLET
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=4d4e488d-45d6-4496-b165-c349c67d4f11@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®