From: Ahmad Wicaksono <supersonix03@gmail.com>
To: bpf@vger.kernel.org
Cc: rhkrqnwk98@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, john.fastabend@gmail.com, corbet@lwn.net,
linux-doc@vger.kernel.org,
Ahmad Wicaksono <supersonix03@gmail.com>
Subject: [PATCH bpf-next 0/2] Documentation/bpf: Fix stale references in map docs
Date: Sun, 15 Nov 2026 00:01:15 +0700 [thread overview]
Message-ID: <20261114170117.196552-1-supersonix03@gmail.com> (raw)
Two documentation fixes for the BPF map pages.
Patch 1 records that since commit be39165224d0 ("bpf, sockmap: Disallow
update and delete from tc, xdp, socket_filter and flow_dissector"), only
BPF_TRACE_ITER tracing, sock_ops (delete only), sk_reuseport and
sk_lookup programs may mutate a sockmap or sockhash; anything else is
rejected with "cannot update sockmap in this context". The kernel-side
sections of map_sockmap.rst did not mention this. It also drops the
reference to progs/test_sockmap_update.c, removed by
commit 5de7a6eaed89 ("selftests/bpf: Drop
tc/xdp/flow_dissector/socket_filter sockmap mutation tests").
Patch 2 fixes two moved selftests paths: test_lpm_map.c, now
map_tests/lpm_trie_map_basic_ops.c, and test_xdp_noinline.c, now under
progs/.
Documentation only; no functional change.
Ahmad Wicaksono (2):
Documentation/bpf: Update sockmap docs for mutation restrictions
Documentation/bpf: Fix stale selftests file references
Documentation/bpf/btf.rst | 2 +-
Documentation/bpf/map_lpm_trie.rst | 6 +++---
Documentation/bpf/map_sockmap.rst | 18 ++++++++++++++++--
3 files changed, 20 insertions(+), 6 deletions(-)
checkpatch.pl --strict is clean. make SPHINXDIRS=bpf htmldocs gives
identical warnings before and after. Documentation only, so nothing to
run-test.
base-commit: ca4181cacb0c6a5632018f1c94f29d9dbc0e9270
--
2.43.0
next reply other threads:[~2026-11-14 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:01 Ahmad Wicaksono [this message]
2026-11-14 17:01 ` [PATCH bpf-next 1/2] Documentation/bpf: Update sockmap docs for mutation restrictions Ahmad Wicaksono
2026-11-16 18:51 ` Jakub Sitnicki
2026-11-17 5:10 ` Alexei Starovoitov
2026-11-14 17:01 ` [PATCH bpf-next 2/2] Documentation/bpf: Fix stale selftests file references Ahmad Wicaksono
2026-11-16 18:52 ` Jakub Sitnicki
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=20261114170117.196552-1-supersonix03@gmail.com \
--to=supersonix03@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rhkrqnwk98@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.