From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <kees@kernel.org>
Cc: ast@kernel.org, jolsa@kernel.org, sun.jian.kdev@gmail.com,
andrii@kernel.org, eddyz87@gmail.com, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, bpf@vger.kernel.org, memxor@gmail.com,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v5] libbpf: Use strscpy() in kernel code for skel_map_create()
Date: Wed, 13 May 2026 18:03:17 +0000 [thread overview]
Message-ID: <177869539730.3760421.10737423823737743835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260513050806.do.620-kees@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 12 May 2026 22:08:07 -0700 you wrote:
> Linux has deprecated[1] strncpy(), and the use in skel_map_create()
> is best replaced with strscpy(). Since we still need to build this
> file in userspace, leave the strncpy() in place in that case. This
> is the last use of strncpy() in the kernel.
>
> Link: https://github.com/KSPP/linux/issues/90 [1]
> Signed-off-by: Kees Cook <kees@kernel.org>
>
> [...]
Here is the summary with links:
- [v5] libbpf: Use strscpy() in kernel code for skel_map_create()
https://git.kernel.org/bpf/bpf-next/c/74a9bb761a43
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-05-13 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 5:08 [PATCH v5] libbpf: Use strscpy() in kernel code for skel_map_create() Kees Cook
2026-05-13 18:03 ` patchwork-bot+netdevbpf [this message]
2026-05-14 1:56 ` sashiko-bot
2026-05-14 3:20 ` Kees Cook
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=177869539730.3760421.10737423823737743835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=sun.jian.kdev@gmail.com \
--cc=yonghong.song@linux.dev \
/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.