From: Adethya Srinivasan <adethyasrinivasan@outlook.com>
To: bpf@vger.kernel.org
Cc: Adethya Srinivasan <adethyasrinivasan@outlook.com>,
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: [PATCH bpf v2 0/2] Reject writable map iterators on read-only maps
Date: Thu, 12 Nov 2026 15:54:05 +0000 [thread overview]
Message-ID: <LO2P302MB0197C0434BCC2A9031E99A18BC702@LO2P302MB0197.GBRP302.PROD.OUTLOOK.COM> (raw)
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.
Changes in v2:
- Check BPF_F_RDONLY_PROG only; drop the frozen-map check.
- Shorten the commit message and correct the Fixes tags.
- Add a selftest expecting -EACCES when attaching dump_bpf_array_map()
to a BPF_F_RDONLY_PROG array.
Adethya Srinivasan (2):
bpf: Reject writable map iterators on read-only maps
selftests/bpf: Check writable iterator attach to a read-only array
kernel/bpf/map_iter.c | 12 +++++--
.../selftests/bpf/prog_tests/bpf_iter.c | 35 +++++++++++++++++++
2 files changed, 44 insertions(+), 3 deletions(-)
next reply other threads:[~2026-11-12 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 15:54 Adethya Srinivasan [this message]
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
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=LO2P302MB0197C0434BCC2A9031E99A18BC702@LO2P302MB0197.GBRP302.PROD.OUTLOOK.COM \
--to=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®