From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Ren Wei" <weir@nebusec.ai>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>
Cc: <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>,
<emil@etsalapatis.com>, <ihor.solodrai@linux.dev>,
<john.fastabend@gmail.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <hawk@kernel.org>, <sdf@fomichev.me>,
<drosen@google.com>, <ameryhung@gmail.com>,
<xyx2021@mail.ustc.edu.cn>, <chenyy23@mails.tsinghua.edu.cn>,
<vega@nebusec.ai>, <rakukuip@gmail.com>
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Reject packet dynptr slices in mutating helpers and subprograms
Date: Sun, 18 Oct 2026 15:36:07 +0000 [thread overview]
Message-ID: <DM82PN9SLID5.ZJSU0JDPQAA6@gmail.com> (raw)
In-Reply-To: <cover.1792222148.git.rakukuip@gmail.com>
On Sat, Oct 17, 2026 at 10:44 PM Ren Wei <weir@nebusec.ai> wrote:
> This series resolves the problem across mutating helpers and subprograms:
Not anymore. This doesn't apply to bpf-next, because it was fixed there
a few hours before you sent v2:
a6f8a67c13dd ("bpf: Refuse packet slices for packet-changing helpers")
19e6ca6b4a22 ("bpf: Drop packet pointers behind kfuncs writing an skb")
589998616e0f ("bpf: Let bpf_dynptr_write() mark a global function")
b7f97db88948 ("bpf: Don't take a dynptr argument for a local dynptr")
1c19f2b3b2f3 ("bpf: Follow the head if an skb is written from a slice")
check_func_arg() rejects the PoC with "function access to the packet is
not allowed".
pw-bot: cr
prev parent reply other threads:[~2026-10-18 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 5:44 [PATCH bpf-next v2 0/2] bpf: Reject packet dynptr slices in mutating helpers and subprograms Ren Wei
2026-10-18 5:44 ` [PATCH bpf-next v2 1/2] " Ren Wei
2026-10-18 6:23 ` sashiko-bot
2026-10-18 5:44 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test rejection of packet dynptr slices in mutating helpers Ren Wei
2026-10-18 5:53 ` sashiko-bot
2026-10-18 15:36 ` Alexei Starovoitov [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=DM82PN9SLID5.ZJSU0JDPQAA6@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyy23@mails.tsinghua.edu.cn \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=drosen@google.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=hawk@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rakukuip@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
--cc=xyx2021@mail.ustc.edu.cn \
--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.