public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: "Álvaro Costa" <alvaroc.dev@gmail•com>
Cc: jiri@resnulli•us, "David S. Miller" <davem@davemloft•net>,
	Eric Dumazet <edumazet@google•com>,
	Paolo Abeni <pabeni@redhat•com>, Simon Horman <horms@kernel•org>,
	netdev@vger•kernel.org
Subject: Re: [PATCH] devlink/param: replace deprecated strcpy() with strscpy()
Date: Thu, 23 Apr 2026 18:31:14 -0700	[thread overview]
Message-ID: <20260423183114.560396c1@kernel.org> (raw)
In-Reply-To: <20260424012037.89619-1-alvaroc.dev@gmail.com>

On Thu, 23 Apr 2026 22:20:22 -0300 Álvaro Costa wrote:
> Replace strcpy() call used to extract a string parameter from param_data
> with strscpy(). Since strscpy() already performs bounds checking and
> ensures the destination string is NUL-terminated, remove the string
> length check as well.

## Form letter - net-next-closed

We have already submitted our pull request with net-next material for v7.1,
and therefore net-next is closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.

Please repost when net-next reopens after Apr 27th.

RFC patches sent for review only are obviously welcome at any time.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
-- 
pw-bot: defer
pv-bot: closed


  reply	other threads:[~2026-04-24  1:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  1:20 [PATCH] devlink/param: replace deprecated strcpy() with strscpy() Álvaro Costa
2026-04-24  1:31 ` Jakub Kicinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-06 21:14 Álvaro Costa
2026-05-06 22:42 ` Jakub Kicinski
2026-05-06 23:52   ` Álvaro Costa
2026-05-07  8:04 ` David Laight
2026-05-07 14:52   ` Jakub Kicinski
2026-05-07 21:10     ` David Laight

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=20260423183114.560396c1@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=alvaroc.dev@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=jiri@resnulli$(echo .)us \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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