BPF List
 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 v2 bpf-next 0/3] Fix libbpf BPF skeleton forward/backward compat
Date: Wed, 10 Jul 2024 02:10:31 +0000	[thread overview]
Message-ID: <172057743108.1917.580054394368940459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240708204540.4188946-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon,  8 Jul 2024 13:45:37 -0700 you wrote:
> Fix recently identified (but long standing) bug with handling BPF skeleton
> forward and backward compatibility. On libbpf side, even though BPF skeleton
> was always designed to be forward and backwards compatible through recording
> actual size of constrituents of BPF skeleton itself (map/prog/var skeleton
> definitions), libbpf implementation did implicitly hard-code those sizes by
> virtue of using a trivial array access syntax.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/3] bpftool: improve skeleton backwards compat with old buggy libbpfs
    https://git.kernel.org/bpf/bpf-next/c/06e71ad53488
  - [v2,bpf-next,2/3] libbpf: fix BPF skeleton forward/backward compat handling
    https://git.kernel.org/bpf/bpf-next/c/99fb9531886d
  - [v2,bpf-next,3/3] libbpf: improve old BPF skeleton handling for map auto-attach
    https://git.kernel.org/bpf/bpf-next/c/a459f4bb27f2

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-07-10  2:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 20:45 [PATCH v2 bpf-next 0/3] Fix libbpf BPF skeleton forward/backward compat Andrii Nakryiko
2024-07-08 20:45 ` [PATCH v2 bpf-next 1/3] bpftool: improve skeleton backwards compat with old buggy libbpfs Andrii Nakryiko
2024-07-08 22:16   ` Eduard Zingerman
2024-07-08 22:54   ` Eduard Zingerman
2024-07-08 23:20     ` Andrii Nakryiko
2024-07-08 20:45 ` [PATCH v2 bpf-next 2/3] libbpf: fix BPF skeleton forward/backward compat handling Andrii Nakryiko
2024-07-08 20:45 ` [PATCH v2 bpf-next 3/3] libbpf: improve old BPF skeleton handling for map auto-attach Andrii Nakryiko
2024-07-08 23:09   ` Eduard Zingerman
2024-07-10  2:10 ` 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=172057743108.1917.580054394368940459.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox