From: Martin KaFai Lau <martin.lau@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: validate nulled-out struct_ops program is handled properly
Date: Mon, 29 Apr 2024 16:46:52 -0700 [thread overview]
Message-ID: <0df9d83b-aaa4-45d8-abae-d20fee8a6213@linux.dev> (raw)
In-Reply-To: <CAEf4BzYo+wCE_dg1kx-dA9egvz7KE6tPS0fzFgeaCgx02+NrcQ@mail.gmail.com>
On 4/29/24 3:35 PM, Andrii Nakryiko wrote:
> On Mon, Apr 29, 2024 at 2:29 PM Martin KaFai Lau <martin.lau@linux.dev> wrote:
>>
>> On 4/27/24 8:09 PM, Andrii Nakryiko wrote:
>>> Add a selftests validating that it's possible to have some struct_ops
>>> callback set declaratively, then disable it (by setting to NULL)
>>> programmatically. Libbpf should detect that such program should be
>>
>> such program should be /not/ loaded ?
>
> yep, can you fix it up while applying or should I send a new revision?
I will take care of it. No need to respin.
next prev parent reply other threads:[~2024-04-29 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 3:09 [PATCH bpf-next 1/2] libbpf: handle nulled-out program in struct_ops correctly Andrii Nakryiko
2024-04-28 3:09 ` [PATCH bpf-next 2/2] selftests/bpf: validate nulled-out struct_ops program is handled properly Andrii Nakryiko
2024-04-29 21:29 ` Martin KaFai Lau
2024-04-29 22:35 ` Andrii Nakryiko
2024-04-29 23:46 ` Martin KaFai Lau [this message]
2024-04-30 0:00 ` [PATCH bpf-next 1/2] libbpf: handle nulled-out program in struct_ops correctly patchwork-bot+netdevbpf
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=0df9d83b-aaa4-45d8-abae-d20fee8a6213@linux.dev \
--to=martin.lau@linux.dev \
--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 \
/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.