From: Ruben Wauters <rubenru09@aol.com>
To: 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
Cc: Ruben Wauters <rubenru09@aol.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH RESEND] x86/cpu/intel: replace deprecated strcpy with strscpy
Date: Mon, 30 Jun 2025 15:29:30 +0100 [thread overview]
Message-ID: <20250630143225.6059-1-rubenru09@aol.com> (raw)
In-Reply-To: <20250630143225.6059-1-rubenru09.ref@aol.com>
strcpy is deprecated due to lack of bounds checking.
This patch replaces strcpy with strscpy, the recommended alternative for
null terminated strings, to follow best practices.
Signed-off-by: Ruben Wauters <rubenru09@aol.com>
---
This patch was reviewed by H. Peter Anvin and (by my understanding)
was deemed ok to apply. I have not added a Reviewed-by tag as H.
Peter Anvin did not do so.
The last time I resent this patch was during the merge window so it
understandably did not get applied or further reviewed.
I have resent it again as the merge window has now closed, hopefully
so it can be further reviewed and applied
---
arch/x86/kernel/cpu/intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
index 584dd55bf739..b49bba30434d 100644
--- a/arch/x86/kernel/cpu/intel.c
+++ b/arch/x86/kernel/cpu/intel.c
@@ -607,7 +607,7 @@ static void init_intel(struct cpuinfo_x86 *c)
}
if (p)
- strcpy(c->x86_model_id, p);
+ strscpy(c->x86_model_id, p);
}
#endif
--
2.48.1
next parent reply other threads:[~2025-06-30 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250630143225.6059-1-rubenru09.ref@aol.com>
2025-06-30 14:29 ` Ruben Wauters [this message]
2025-08-20 14:03 ` Borislav Petkov
[not found] <20250520133549.9964-1-rubenru09.ref@aol.com>
2025-05-20 13:26 ` Ruben Wauters
2025-05-28 15:34 ` Ruben Wauters
2025-05-28 17:09 ` Borislav Petkov
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=20250630143225.6059-1-rubenru09@aol.com \
--to=rubenru09@aol.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--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®