From: Yonghong Song <yonghong.song@linux.dev>
To: Yafang Shao <laoar.shao@gmail.com>,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 3/3] libbpf: Check the return value of bpf_iter_<type>_new()
Date: Thu, 8 Feb 2024 09:43:29 -0800 [thread overview]
Message-ID: <4e79dc07-ba34-49e3-92fe-a5f2c96045ee@linux.dev> (raw)
In-Reply-To: <20240208090906.56337-4-laoar.shao@gmail.com>
On 2/8/24 1:09 AM, Yafang Shao wrote:
> On success, bpf_iter_<type>_new() return 0. On failure, it returns ERR.
> We'd better check the return value of it.
Not sure whether this patch is necessary or not.
I checked:
bpf_iter_num_{new,next}
bpf_iter_task_vma_{new,next}
bpf_iter_css_task_{new,next}
It looks like the convention is for *_next() return NULL or not
instead of relying on return value of _new() to decide whether to
proceed or not. Maybe Andrii can clarify.
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> ---
> tools/lib/bpf/bpf_helpers.h | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/tools/lib/bpf/bpf_helpers.h b/tools/lib/bpf/bpf_helpers.h
> index 79eaa581be98..2cd2428e3bc6 100644
> --- a/tools/lib/bpf/bpf_helpers.h
> +++ b/tools/lib/bpf/bpf_helpers.h
> @@ -133,6 +133,15 @@
> # define __bpf_unreachable() __builtin_trap()
> #endif
>
> +#ifndef __must_check
> +#define __must_check __attribute__((warn_unused_result))
> +#endif
> +
> +static inline void * __must_check ERR_PTR(long error)
> +{
> + return (void *) error;
> +}
> +
> /*
> * Helper function to perform a tail call with a constant/immediate map slot.
> */
> @@ -340,14 +349,13 @@ extern void bpf_iter_num_destroy(struct bpf_iter_num *it) __weak __ksym;
> /* initialize and define destructor */ \
> struct bpf_iter_##type ___it __attribute__((aligned(8), /* enforce, just in case */, \
> cleanup(bpf_iter_##type##_destroy))), \
> - /* ___p pointer is just to call bpf_iter_##type##_new() *once* to init ___it */ \
> *___p __attribute__((unused)) = ( \
> - bpf_iter_##type##_new(&___it, ##args), \
> /* this is a workaround for Clang bug: it currently doesn't emit BTF */ \
> /* for bpf_iter_##type##_destroy() when used from cleanup() attribute */ \
> - (void)bpf_iter_##type##_destroy, (void *)0); \
> + (void)bpf_iter_##type##_destroy, \
> + ERR_PTR(bpf_iter_##type##_new(&___it, ##args))); \
> /* iteration and termination check */ \
> - (((cur) = bpf_iter_##type##_next(&___it))); \
> + ((!___p) && ((cur) = bpf_iter_##type##_next(&___it))); \
> )
> #endif /* bpf_for_each */
>
next prev parent reply other threads:[~2024-02-08 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 9:09 [PATCH bpf-next 0/3] bpf: Fix an issue in bpf_iter_task Yafang Shao
2024-02-08 9:09 ` [PATCH bpf-next 1/3] bpf: Fix an issue due to uninitialized bpf_iter_task Yafang Shao
2024-02-08 9:41 ` Chuyi Zhou
2024-02-08 9:48 ` Yafang Shao
2024-02-08 15:52 ` Yonghong Song
2024-02-08 17:21 ` Alexei Starovoitov
2024-02-08 9:09 ` [PATCH bpf-next 2/3] selftests/bpf: Add negtive test cases for task iter Yafang Shao
2024-02-08 9:09 ` [PATCH bpf-next 3/3] libbpf: Check the return value of bpf_iter_<type>_new() Yafang Shao
2024-02-08 17:43 ` Yonghong Song [this message]
2024-02-08 18:56 ` 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=4e79dc07-ba34-49e3-92fe-a5f2c96045ee@linux.dev \
--to=yonghong.song@linux.dev \
--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=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.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