From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
sinquersw@gmail.com, kuifeng@meta.com
Subject: Re: [PATCH bpf-next v2 0/3] Ignore additional fields in the struct_ops maps in an updated version.
Date: Thu, 14 Mar 2024 21:00:31 +0000 [thread overview]
Message-ID: <171045003158.27753.767457664957549262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313214139.685112-1-thinker.li@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 13 Mar 2024 14:41:36 -0700 you wrote:
> According to an offline discussion, it would be beneficial to
> implement a backward-compatible method for struct_ops types with
> additional fields that are not present in older kernels.
>
> This patchset accepts additional fields of a struct_ops map with all
> zero values even if these fields are not in the corresponding type in
> the kernel. This provides a way to be backward compatible. User space
> programs can use the same map on a machine running an old kernel by
> clearing fields that do not exist in the kernel.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] libbpf: Skip zeroed or null fields if not found in the kernel type.
https://git.kernel.org/bpf/bpf-next/c/c911fc61a7ce
- [bpf-next,v2,2/3] selftests/bpf: Ensure libbpf skip all-zeros fields of struct_ops maps.
https://git.kernel.org/bpf/bpf-next/c/26a7cf2bbea6
- [bpf-next,v2,3/3] selftests/bpf: Accept extra arguments if they are not used.
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-14 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:41 [PATCH bpf-next v2 0/3] Ignore additional fields in the struct_ops maps in an updated version Kui-Feng Lee
2024-03-13 21:41 ` [PATCH bpf-next v2 1/3] libbpf: Skip zeroed or null fields if not found in the kernel type Kui-Feng Lee
2024-03-13 21:41 ` [PATCH bpf-next v2 2/3] selftests/bpf: Ensure libbpf skip all-zeros fields of struct_ops maps Kui-Feng Lee
2024-03-13 21:41 ` [PATCH bpf-next v2 3/3] selftests/bpf: Accept extra arguments if they are not used Kui-Feng Lee
2024-03-14 20:59 ` [PATCH bpf-next v2 0/3] Ignore additional fields in the struct_ops maps in an updated version Andrii Nakryiko
2024-03-15 23:44 ` Kui-Feng Lee
2024-03-18 18:34 ` Andrii Nakryiko
2024-03-18 21:08 ` Kui-Feng Lee
2024-03-14 21: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=171045003158.27753.767457664957549262.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=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sinquersw@gmail.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.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