From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Ahmad Wicaksono" <supersonix03@gmail.com>, <bpf@vger.kernel.org>
Cc: <rhkrqnwk98@gmail.com>, <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>
Subject: Re: [PATCH bpf-next 1/2] Documentation/bpf: Update sockmap docs for mutation restrictions
Date: Tue, 17 Nov 2026 05:10:57 +0000 [thread overview]
Message-ID: <DMX87BV331FW.XJL0Y10TBDO2@gmail.com> (raw)
In-Reply-To: <20261114170117.196552-2-supersonix03@gmail.com>
On Sat, Nov 14, 2026 at 09:01 AM Ahmad Wicaksono <supersonix03@gmail.com> wrote:
> +.. note::
> + The verifier only accepts this helper on a sockmap or sockhash from
> + ``BPF_PROG_TYPE_SK_REUSEPORT`` and ``BPF_PROG_TYPE_SK_LOOKUP``
> + programs, and from ``BPF_PROG_TYPE_TRACING`` programs attached as
> + ``BPF_TRACE_ITER``. Other program types, such as tc, XDP,
This already not accurate after Michal's series narrowed BPF_TRACE_ITER to iter/sockmap:
https://lore.kernel.org/bpf/20261107-sockmap-update-limit-iter-v3-2-7c0bad1ad036@rbox.co/
Pls wait for bpf tree to make it to bpf-next and resend keeping acks.
pw-bot: cr
next prev parent reply other threads:[~2026-11-17 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:01 [PATCH bpf-next 0/2] Documentation/bpf: Fix stale references in map docs Ahmad Wicaksono
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 [this message]
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=DMX87BV331FW.XJL0Y10TBDO2@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@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=supersonix03@gmail.com \
--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.