BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, bpf@vger.kernel.org,
	qmo@kernel.org, hi@tychen.cc, kpsingh@kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Don't echo user-supplied map info fields back to userspace
Date: Sat, 17 Oct 2026 01:50:04 +0000	[thread overview]
Message-ID: <179220180452.1055958.11274248760332929964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016191635.662690-1-daniel@iogearbox.net>

Hello:

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

On Fri, 16 Oct 2026 21:16:35 +0200 you wrote:
> Commit ea2e6467ac36 ("bpf: Return hashes of maps in BPF_OBJ_GET_INFO_BY_FD")
> started copying struct bpf_map_info in from userspace in order to read
> the new hash and hash_size input fields. Before that, the kernel ignored
> the contents of the user buffer and returned a zeroed structure with only
> the output fields filled in.
> 
> Some output fields are only set for certain maps: btf_id, btf_key_type_id
> and btf_value_type_id when the map has BTF (and btf_vmlinux_id for
> struct_ops maps, ifindex, netns_dev and netns_ino when the map is
> offloaded). For all other maps, these fields now return whatever
> userspace passed in before.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] bpf: Don't echo user-supplied map info fields back to userspace
    https://git.kernel.org/bpf/bpf-next/c/458575e1f2dd

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



      reply	other threads:[~2026-10-17  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 19:16 [PATCH bpf-next v2] bpf: Don't echo user-supplied map info fields back to userspace Daniel Borkmann
2026-10-17  1:50 ` 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=179220180452.1055958.11274248760332929964.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=hi@tychen.cc \
    --cc=kpsingh@kernel.org \
    --cc=qmo@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