public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
	andrii@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
	eddyz87@gmail.com, yatsenko@meta.com, martin.lau@kernel.org,
	ameryhung@gmail.com, kernel-team@meta.com
Subject: [PATCH bpf-next v2 0/1] Refactor dynptr mutability tracking
Date: Wed,  1 Apr 2026 23:50:12 -0700	[thread overview]
Message-ID: <20260402065013.884228-1-ameryhung@gmail.com> (raw)

A heads up that this independent patch is separated from the object
relation tracking refactor patchset [0] to breakup the larger patchset
and make the review easier.

[0] https://lore.kernel.org/bpf/20260307064439.3247440-1-ameryhung@gmail.com/

v1 -> v2
 - Change the definition of the mutatbility of bpf_dynptr
   to only bpf_dynptr->data instead of the whole structure. Basically,
   only care about preventing passing CONST_PTR_TO_DYNPTR to arguments
   tagged with OBJ_RELEASE or MEM_UNINT
 - Drop MEM_RDONLY annotation as now we dont care
 - Drop passing CONST_PTR_TO_DYNPTR to MEM_RDONLY kfunc selftest
   

Amery Hung (1):
  bpf: Refactor dynptr mutability tracking

 fs/verity/measure.c                           |  2 +-
 include/linux/bpf.h                           |  8 +--
 kernel/bpf/btf.c                              |  2 +-
 kernel/bpf/helpers.c                          | 18 ++---
 kernel/bpf/verifier.c                         | 68 +++++--------------
 kernel/trace/bpf_trace.c                      | 18 ++---
 tools/testing/selftests/bpf/bpf_kfuncs.h      |  8 +--
 .../selftests/bpf/progs/dynptr_success.c      |  6 +-
 .../bpf/progs/test_kfunc_dynptr_param.c       |  9 +--
 9 files changed, 51 insertions(+), 88 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-04-02  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  6:50 Amery Hung [this message]
2026-04-02  6:50 ` [PATCH bpf-next v2 1/1] bpf: Refactor dynptr mutability tracking Amery Hung

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=20260402065013.884228-1-ameryhung@gmail.com \
    --to=ameryhung@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=yatsenko@meta.com \
    /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