mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Blum <thorsten.blum@linux.dev>
To: Andreas Larsson <andreas@gaisler.com>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-hardening@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] sparc: PCI: Replace deprecated strcpy() with strscpy()
Date: Mon, 22 Sep 2025 23:11:01 +0200	[thread overview]
Message-ID: <57FABB07-3C1B-4D33-A5BB-8D402A20487F@linux.dev> (raw)
In-Reply-To: <d676606e-f448-434b-be26-c839dea4f5d1@gaisler.com>

Hi Andreas,

On 19. Sep 2025, Andreas Larsson wrote:
> 
> 
> On 2025-09-17 17:50, Bjorn Helgaas wrote:
>> On Wed, Sep 17, 2025 at 04:47:30PM +0200, Thorsten Blum wrote:
>>> strcpy() is deprecated; use strscpy() instead.
>>> 
>>> No functional changes intended.
>>> 
>>> Link: https://github.com/KSPP/linux/issues/88
>>> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>> 
>> No objection from me, but no particular PCI core issue and I don't
>> maintain this file, so up to the sparc folks if they want it.
>> 
>> I would consider making a single patch to address this issue
>> everywhere in arch/sparc so it can all be reviewed together.
> 
> Thank you and sorry for the late feedback. I agree with the above.
> Thorsten, could you fix this for all occurrences of strcpy() in
> arch/sparc?

I just submitted a small series [1] replacing all occurrences of strcpy
in arch/sparc.

Thanks,
Thorsten

[1] https://lore.kernel.org/lkml/20250922210408.1723452-1-thorsten.blum@linux.dev/


  reply	other threads:[~2025-09-22 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 14:47 Thorsten Blum
2025-09-17 15:50 ` Bjorn Helgaas
2025-09-19 18:13   ` Andreas Larsson
2025-09-22 21:11     ` Thorsten Blum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-17 23:23 Thorsten Blum
2025-05-21 12:17 Thorsten Blum

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=57FABB07-3C1B-4D33-A5BB-8D402A20487F@linux.dev \
    --to=thorsten.blum@linux.dev \
    --cc=andreas@gaisler.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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
all inboxes | Powered by JetHome®