From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net,
david.laight@aculab.com, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
martin.lau@linux.dev, mykolal@fb.com, rongtao@cestc.cn,
sdf@google.com, shuah@kernel.org, song@kernel.org, yhs@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: cgroup_helpers.c: Fix strncpy() fortify warning
Date: Fri, 04 Nov 2022 22:50:15 +0000 [thread overview]
Message-ID: <166760221576.27361.8207434405001811248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_469D8AF32BD56816A29981BED06E96D22506@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 4 Nov 2022 09:27:54 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Copy libbpf_strlcpy() from libbpf_internal.h to bpf_util.h, and rename it
> to bpf_strlcpy(), then replace selftests strncpy()/libbpf_strlcpy() with
> bpf_strlcpy(), fix compile warning.
>
> The libbpf_internal.h header cannot be used directly here, because
> references to cgroup_helpers.c in samples/bpf will generate compilation
> errors. We also can't add libbpf_strlcpy() directly to bpf_util.h,
> because the definition of libbpf_strlcpy() in libbpf_internal.h is
> duplicated. In order not to modify the libbpf code, add a new function
> bpf_strlcpy() to selftests bpf_util.h.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: cgroup_helpers.c: Fix strncpy() fortify warning
https://git.kernel.org/bpf/bpf-next/c/b3c09fdca113
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:[~2022-11-04 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 11:33 [PATCH bpf-next] selftests/bpf: Fix strncpy() fortify warning Rong Tao
2022-10-27 20:09 ` Andrii Nakryiko
2022-10-28 0:26 ` Re: [PATCH] " Rong Tao
2022-10-28 17:08 ` Andrii Nakryiko
2022-10-29 2:59 ` [PATCH bpf-next] " Rong Tao
2022-10-29 12:23 ` David Laight
2022-11-01 9:25 ` Rong Tao
2022-11-01 9:27 ` David Laight
2022-11-01 12:21 ` Rong Tao
2022-11-01 13:56 ` Daniel Borkmann
2022-11-01 14:23 ` Rong Tao
2022-11-01 15:46 ` Daniel Borkmann
2022-11-02 12:59 ` [PATCH bpf-next] selftests/bpf: cgroup_helpers.c: " Rong Tao
2022-11-03 18:45 ` Andrii Nakryiko
2022-11-04 1:27 ` Rong Tao
2022-11-04 22:50 ` patchwork-bot+netdevbpf [this message]
2022-10-29 3:07 ` [RESEND PATCH bpf-next] selftests/bpf: " Rong Tao
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=166760221576.27361.8207434405001811248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=david.laight@aculab.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox