From: patchwork-bot+netdevbpf@kernel.org
To: Ruben Wauters <rubenru09@aol.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next] ipv4: ip_tunnel: Replace strcpy use with strscpy
Date: Tue, 06 May 2025 01:40:33 +0000 [thread overview]
Message-ID: <174649563350.1007977.12065018765324353318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250501202935.46318-1-rubenru09@aol.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 1 May 2025 21:23:55 +0100 you wrote:
> Use of strcpy is decpreated, replaces the use of strcpy with strscpy as
> recommended.
>
> strscpy was chosen as it requires a NUL terminated non-padded string,
> which is the case here.
>
> I am aware there is an explicit bounds check above the second instance,
> however using strscpy protects against buffer overflows in any future
> code, and there is no good reason I can see to not use it.
>
> [...]
Here is the summary with links:
- [v2,net-next] ipv4: ip_tunnel: Replace strcpy use with strscpy
https://git.kernel.org/netdev/net-next/c/c2dbda07662e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-06 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250501202935.46318-1-rubenru09.ref@aol.com>
2025-05-01 20:23 ` [PATCH v2 net-next] ipv4: ip_tunnel: Replace strcpy use with strscpy Ruben Wauters
2025-05-06 1:40 ` patchwork-bot+netdevbpf [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=174649563350.1007977.12065018765324353318.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rubenru09@aol.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.