BPF List
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@meta.com>
To: "Toke Høiland-Jørgensen" <toke@kernel.org>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"ast@kernel.org" <ast@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	"martin.lau@kernel.org" <martin.lau@kernel.org>,
	Kernel Team <kernel-team@meta.com>
Subject: Re: [PATCH bpf] bpf: fix bpf_dynptr_slice() returning ERR_PTR() on erro
Date: Thu, 2 Nov 2023 18:11:40 +0000	[thread overview]
Message-ID: <980EFFAB-A79F-4B18-BCA7-52277939A5DC@fb.com> (raw)
In-Reply-To: <874ji4111d.fsf@toke.dk>



> On Nov 2, 2023, at 11:07 AM, Toke Høiland-Jørgensen <toke@kernel.org> wrote:
> 
> Andrii Nakryiko <andrii.nakryiko@gmail.com> writes:
> 
>> On Thu, Nov 2, 2023 at 10:55 AM Toke Høiland-Jørgensen <toke@kernel.org> wrote:
>>> 
>>> Andrii Nakryiko <andrii@kernel.org> writes:
>>> 
>>>> Let's fix it for real this time. It shouldn't just detect ERR_PTR()
>>>> return from bpf_xdp_pointer(), but also turn that into NULL to follow
>>>> bpf_dynptr_slice() contract.
>>>> 
>>>> Fixes: 5426700e6841 ("bpf: fix bpf_dynptr_slice() to stop return an ERR_PTR.")
>>>> Fixes: 66e3a13e7c2c ("bpf: Add bpf_dynptr_slice and bpf_dynptr_slice_rdwr")
>>>> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
>>>> ---
>>>> kernel/bpf/helpers.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>> 
>>>> diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
>>>> index 56b0c1f678ee..04049097176c 100644
>>>> --- a/kernel/bpf/helpers.c
>>>> +++ b/kernel/bpf/helpers.c
>>>> @@ -2309,7 +2309,7 @@ __bpf_kfunc void *bpf_dynptr_slice(const struct bpf_dynptr_kern *ptr, u32 offset
>>>>      {
>>>>              void *xdp_ptr = bpf_xdp_pointer(ptr->data, ptr->offset + offset, len);
>>>>              if (!IS_ERR_OR_NULL(xdp_ptr))
>>>> -                     return xdp_ptr;
>>>> +                     return NULL;
>>> 
>>> Erm, the check in the if is inverted - so isn't this 'return xdp_ptr'
>>> covering the case where bpf_xdp_pointer() *does* in fact return a valid
>>> pointer?
>>> 
>> 
>> Ah, you are right, I missed the ! part... Ok, then I don't think we
>> have an issue, great. Thanks for double checking!
>> Perhaps we should add a simple comment "/* we got a valid direct
>> pointer, return it */", as this looks like an error-handling case.
> 
> Yup, totally agree it's confusing, I had to look at the code three or
> four times as well just now, to be sure that it wasn't buggy. Adding a
> comment would certainly be useful! :)

Aha, I was confused by this for more than a month. I am glad this is 
not an issue. 

Thanks,
Song


      reply	other threads:[~2023-11-02 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 17:26 [PATCH bpf] bpf: fix bpf_dynptr_slice() returning ERR_PTR() on erro Andrii Nakryiko
2023-11-02 17:55 ` Toke Høiland-Jørgensen
2023-11-02 18:00   ` Andrii Nakryiko
2023-11-02 18:07     ` Toke Høiland-Jørgensen
2023-11-02 18:11       ` Song Liu [this message]

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=980EFFAB-A79F-4B18-BCA7-52277939A5DC@fb.com \
    --to=songliubraving@meta.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=toke@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