From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Ning Ding" <dingning04@gmail.com>
Cc: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <martin.lau@linux.dev>,
<davem@davemloft.net>, <greg@kroah.com>
Subject: Re: [PATCH bpf v2 2/2] bpf: Reject untrusted pointers in refcount_acquire
Date: Mon, 03 Aug 2026 09:48:22 +0200 [thread overview]
Message-ID: <DKF56470QYCP.3SPZ9DJ1AVLOK@gmail.com> (raw)
In-Reply-To: <CAJP4iuvL2=72SUwjHeN7mDLKOSkM-KKvBVYrE40R+rnOJs9P-w@mail.gmail.com>
On Mon Aug 3, 2026 at 9:44 AM CEST, Ning Ding wrote:
>> In addition, I would add a comment saying that the BPF_WRITE case for the
>> type_is_untrusted_ptr_alloc_obj() types was already rejected earlier, so this
>> check only permits reads on them.
>
> Thanks, I’m preparing the respin and will check every
> type_is_ptr_alloc_obj() caller to decide whether it should use the new
> stricter one or stay the same.
Sounds good. I'd still keep type_is_ptr_alloc_obj() as the naming for stricter
one, but auditing all users sounds good. On quick skim I don't think we need to
relax anything except this case.
prev parent reply other threads:[~2026-08-03 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 23:50 [PATCH bpf v2 0/2] bpf: Fix refcount_acquire handling for borrowed kptrs Ning Ding
2026-07-26 23:50 ` [PATCH bpf v2 1/2] bpf: Keep refcount_acquire nullable for borrowed RCU kptrs Ning Ding
2026-07-27 4:50 ` Greg KH
2026-07-26 23:50 ` [PATCH bpf v2 2/2] bpf: Reject untrusted pointers in refcount_acquire Ning Ding
2026-07-27 0:13 ` sashiko-bot
2026-07-27 0:40 ` Ning Ding
2026-07-27 4:50 ` Greg KH
2026-08-02 23:29 ` Kumar Kartikeya Dwivedi
2026-08-03 5:57 ` Ning Ding
2026-08-03 6:08 ` Kumar Kartikeya Dwivedi
2026-08-03 6:48 ` Ning Ding
2026-08-03 6:50 ` Kumar Kartikeya Dwivedi
2026-08-03 7:10 ` Ning Ding
2026-08-03 7:21 ` Kumar Kartikeya Dwivedi
2026-08-03 7:44 ` Ning Ding
2026-08-03 7:48 ` Kumar Kartikeya Dwivedi [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=DKF56470QYCP.3SPZ9DJ1AVLOK@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dingning04@gmail.com \
--cc=eddyz87@gmail.com \
--cc=greg@kroah.com \
--cc=martin.lau@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