From: patchwork-bot+netdevbpf@kernel.org
To: Adethya Srinivasan <adethyasrinivasan@outlook.com>
Cc: bpf@vger.kernel.org, yonghong.song@linux.dev, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf v2 0/2] Reject writable map iterators on read-only maps
Date: Thu, 12 Nov 2026 20:10:06 +0000 [thread overview]
Message-ID: <179451420628.625762.2223208572511592827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <LO2P302MB0197C0434BCC2A9031E99A18BC702@LO2P302MB0197.GBRP302.PROD.OUTLOOK.COM>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 12 Nov 2026 15:54:05 +0000 you wrote:
> Reject writable map iterators on BPF_F_RDONLY_PROG maps and add an
> attach-rejection selftest using the existing array-map iterator.
>
> Testing on x86_64 under QEMU:
> - Kernel and test_progs builds passed.
> - Six selected bpf_iter subtests passed, including bpf_array_map_rdonly.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Reject writable map iterators on read-only maps
https://git.kernel.org/bpf/bpf/c/e536074468a2
- [bpf,v2,2/2] selftests/bpf: Check writable iterator attach to a read-only array
https://git.kernel.org/bpf/bpf/c/e1224c9a9053
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:[~2026-11-12 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 15:54 Adethya Srinivasan
2026-11-12 15:54 ` [PATCH bpf v2 1/2] bpf: " Adethya Srinivasan
2026-11-12 15:54 ` [PATCH bpf v2 2/2] selftests/bpf: Check writable iterator attach to a read-only array Adethya Srinivasan
2026-11-12 20: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=179451420628.625762.2223208572511592827.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adethyasrinivasan@outlook.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®