BPF List
 help / color / mirror / Atom feed
From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next v1 0/2] Add __ref annotation for kfuncs
Date: Wed, 27 Jul 2022 10:15:57 +0200	[thread overview]
Message-ID: <20220727081559.24571-1-memxor@gmail.com> (raw)

We decided to delay adding this until a usecase came up, and since now there is
one, instead of KF_TRUSTED_ARGS that applies to all arguments, add a __ref
suffix that has the same effect but only for the argument it is applied to.

Kumar Kartikeya Dwivedi (2):
  bpf: Add support for per-parameter trusted args
  selftests/bpf: Extend KF_TRUSTED_ARGS test for __ref annotation

 Documentation/bpf/kfuncs.rst                 | 18 +++++++++
 kernel/bpf/btf.c                             | 39 +++++++++++++-------
 net/bpf/test_run.c                           |  9 ++++-
 tools/testing/selftests/bpf/verifier/calls.c | 38 +++++++++++++++----
 4 files changed, 81 insertions(+), 23 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-07-27  8:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  8:15 Kumar Kartikeya Dwivedi [this message]
2022-07-27  8:15 ` [PATCH bpf-next v1 1/2] bpf: Add support for per-parameter trusted args Kumar Kartikeya Dwivedi
2022-07-28  7:46   ` Roberto Sassu
2022-07-28  8:18     ` Roberto Sassu
2022-07-28  8:45       ` Kumar Kartikeya Dwivedi
2022-07-28  9:02         ` Kumar Kartikeya Dwivedi
2022-08-02  4:45           ` Alexei Starovoitov
2022-08-02 10:07             ` Roberto Sassu
2022-08-02 15:05               ` Alexei Starovoitov
2022-08-02 16:01                 ` Roberto Sassu
2022-08-03 14:34                   ` Roberto Sassu
2022-07-28  9:02         ` Roberto Sassu
2022-07-27  8:15 ` [PATCH bpf-next v1 2/2] selftests/bpf: Extend KF_TRUSTED_ARGS test for __ref annotation Kumar Kartikeya Dwivedi

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=20220727081559.24571-1-memxor@gmail.com \
    --to=memxor@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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