mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Miguel_Garc=C3=ADa_=3Cmiguelgarciaroman8=40gmail=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
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,
	skhan@linuxfoundation.org
Subject: Re: [PATCH net-next] ipv6: ip6_gre: replace strcpy with strscpy for tunnel name
Date: Wed, 20 Aug 2025 03:11:53 +0000	[thread overview]
Message-ID: <175565951349.3753798.16066239520689231223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818220203.899338-1-miguelgarciaroman8@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 19 Aug 2025 00:02:03 +0200 you wrote:
> Replace the strcpy() call that copies the device name into
> tunnel->parms.name with strscpy(), to avoid potential overflow
> and guarantee NULL termination. This uses the two-argument
> form of strscpy(), where the destination size is inferred
> from the array type.
> 
> Destination is tunnel->parms.name (size IFNAMSIZ).
> 
> [...]

Here is the summary with links:
  - [net-next] ipv6: ip6_gre: replace strcpy with strscpy for tunnel name
    https://git.kernel.org/netdev/net-next/c/09bde6fdcd75

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-08-20  3:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 22:02 Miguel García
2025-08-20  3:11 ` 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=175565951349.3753798.16066239520689231223.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Miguel_Garc=C3=ADa_=3Cmiguelgarciaroman8=40gmail=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.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=skhan@linuxfoundation.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®