From: Yonghong Song <yhs@fb.com>
To: Hao Luo <haoluo@google.com>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
KP Singh <kpsingh@kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v2] bpf/selftests: Test bpf_d_path on rdonly_mem.
Date: Thu, 6 Jan 2022 15:17:21 -0800 [thread overview]
Message-ID: <ca6e2085-251b-1dbd-3ee1-d990b0eec810@fb.com> (raw)
In-Reply-To: <20220106205525.2116218-1-haoluo@google.com>
On 1/6/22 12:55 PM, Hao Luo wrote:
> The second parameter of bpf_d_path() can only accept writable
> memories. Rdonly_mem obtained from bpf_per_cpu_ptr() can not
> be passed into bpf_d_path for modification. This patch adds
> a selftest to verify this behavior.
>
> Signed-off-by: Hao Luo <haoluo@google.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2022-01-06 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 20:55 [PATCH bpf-next v2] bpf/selftests: Test bpf_d_path on rdonly_mem Hao Luo
2022-01-06 23:17 ` Yonghong Song [this message]
2022-01-06 23:25 ` Andrii Nakryiko
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=ca6e2085-251b-1dbd-3ee1-d990b0eec810@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=songliubraving@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