All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: handle nulled-out program in struct_ops correctly
Date: Tue, 30 Apr 2024 00:00:30 +0000	[thread overview]
Message-ID: <171443523045.23001.15781385933394286282.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240428030954.3918764-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Sat, 27 Apr 2024 20:09:53 -0700 you wrote:
> If struct_ops has one of program callbacks set declaratively and host
> kernel is old and doesn't support this callback, libbpf will allow to
> load such struct_ops as long as that callback was explicitly nulled-out
> (presumably through skeleton). This is all working correctly, except we
> won't reset corresponding program slot to NULL before bailing out, which
> will lead to libbpf not detecting that BPF program has to be not
> auto-loaded. Fix this by unconditionally resetting corresponding program
> slot to NULL.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] libbpf: handle nulled-out program in struct_ops correctly
    https://git.kernel.org/bpf/bpf-next/c/f973fccd43d3
  - [bpf-next,2/2] selftests/bpf: validate nulled-out struct_ops program is handled properly
    https://git.kernel.org/bpf/bpf-next/c/1bba3b3d373d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-04-30  0:00 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
2024-04-30  0:00 ` patchwork-bot+netdevbpf [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=171443523045.23001.15781385933394286282.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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.