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,
	kernel-team@fb.com, grantseltzer@gmail.com
Subject: Re: [PATCH bpf-next] libbpf: restore memory layout of bpf_object_open_opts
Date: Fri, 23 Sep 2022 23:30:14 +0000	[thread overview]
Message-ID: <166397581474.8857.10749529299879806327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923230559.666608-1-andrii@kernel.org>

Hello:

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

On Fri, 23 Sep 2022 16:05:59 -0700 you wrote:
> When attach_prog_fd field was removed in libbpf 1.0 and replaced with
> `long: 0` placeholder, it actually shifted all the subsequent fields by
> 8 byte. This is due to `long: 0` promising to adjust next field's offset
> to long-aligned offset. But in this case we were already long-aligned
> as pin_root_path is a pointer. So `long: 0` had no effect, and thus
> didn't feel the gap created by removed attach_prog_fd.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: restore memory layout of bpf_object_open_opts
    https://git.kernel.org/bpf/bpf-next/c/dbdea9b36fb6

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



      reply	other threads:[~2022-09-23 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 23:05 [PATCH bpf-next] libbpf: restore memory layout of bpf_object_open_opts Andrii Nakryiko
2022-09-23 23:30 ` 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=166397581474.8857.10749529299879806327.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=grantseltzer@gmail.com \
    --cc=kernel-team@fb.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