From: Rong Tao <rtoax@foxmail.com>
To: david.laight@aculab.com
Cc: andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, 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,
rtoax@foxmail.com, sdf@google.com, shuah@kernel.org,
song@kernel.org, yhs@fb.com
Subject: Re: RE: [PATCH bpf-next] selftests/bpf: Fix strncpy() fortify warning
Date: Tue, 1 Nov 2022 17:25:12 +0800 [thread overview]
Message-ID: <tencent_5523542A5E3F46AD119B0C0A8588B27E2E09@qq.com> (raw)
In-Reply-To: <1611fe67d311461aa5f820836318bacc@AcuMS.aculab.com>
Can we just use the first patch?
https://lore.kernel.org/lkml/tencent_EE3E19F80ACD66955D26A878BC768CFA210A@qq.com/
next prev parent reply other threads:[~2022-11-01 9:25 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 [this message]
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
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=tencent_5523542A5E3F46AD119B0C0A8588B27E2E09@qq.com \
--to=rtoax@foxmail.com \
--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=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 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.