All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	bpf@vger.kernel.org, linux-mm@kvack.org,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Lorenzo Stoakes <ljs@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Federico Di Pierro <nierro92@gmail.com>
Subject: Re: [PATCHv3 bpf-next 1/8] bpf: Honor const on generic kfunc memory arguments
Date: Fri, 6 Nov 2026 14:52:46 +0100	[thread overview]
Message-ID: <au3brpNZG2nANnha@krava> (raw)
In-Reply-To: <CAEf4BzbdBLb1cBeF0an386k=CmMYKdz=Or5mSjzy_F5SFOwsxg@mail.gmail.com>

On Thu, Nov 05, 2026 at 04:34:44PM -0800, Andrii Nakryiko wrote:

SNIP

> > +/* A kfunc only reads through 'const T *arg'. The compiler enforces it. */
> > +static enum bpf_type_flag kfunc_arg_mem_flag(const struct btf *btf,
> > +                                            const struct btf_param *arg)
> > +{
> > +       const struct btf_type *t = btf_type_skip_modifiers(btf, arg->type, NULL);
> > +       u32 id, ref_id;
> > +
> > +       btf_type_skip_modifiers(btf, t->type, &ref_id);
> > +       for (id = t->type; id != ref_id; id = t->type) {
> > +               t = btf_type_by_id(btf, id);
> > +               if (btf_kind(t) == BTF_KIND_CONST)
> > +                       return MEM_RDONLY;
> > +       }
> 
> quite weird implementation, skip modifier, and then re-walk
> modifiers... while not have a loop from t->type while
> btf_type_is_modifier() and if you find btf_kind(t) == BTF_KIND_CONST
> -> return true?

the intention was not to introduce another helper with modifier
classification, the tradeoff is 2 loops [1]

jirka


[1] https://lore.kernel.org/bpf/DMLRV3E28SC8.3FJZXLBLZI4DD@gmail.com/

> 
> 
> > +       return MEM_WRITE;
> > +}
> > +
> >  static bool is_kfunc_arg_constant(const struct btf *btf, const struct btf_param *arg)
> >  {
> >         return btf_param_match_suffix(btf, arg, "__k");
> > @@ -13618,7 +13634,8 @@ static int resolve_func_arg_type(struct bpf_verifier_env *env,
> >                         PTR_ERR(resolve_ret));
> >                 return -EINVAL;
> >         }
> > -       *arg_type = ARG_PTR_TO_MEM | MEM_FIXED_SIZE | MEM_WRITE |
> > +       *arg_type = ARG_PTR_TO_MEM | MEM_FIXED_SIZE |
> > +                   kfunc_arg_mem_flag(meta->btf, &args[arg]) |
> >                     (*arg_type & (PTR_MAYBE_NULL | MEM_UNINIT));
> >
> >         return 0;
> > @@ -14170,7 +14187,7 @@ get_kfunc_arg_type(struct bpf_verifier_env *env, struct bpf_call_arg_meta *meta,
> >                                 reg_arg_name(env, argno), btf_type_str(ref_t), ref_tname);
> >                         return -EINVAL;
> >                 }
> > -               arg_type = ARG_PTR_TO_MEM | MEM_WRITE;
> > +               arg_type = ARG_PTR_TO_MEM | kfunc_arg_mem_flag(meta->btf, &args[arg]);
> >         } else if (btf_type_is_struct(ref_t))
> >                 /* A pointer to a struct without a size argument is classified as ARG_PTR_TO_BTF_ID */
> >                 arg_type = ARG_PTR_TO_BTF_ID;
> > @@ -14195,7 +14212,8 @@ get_kfunc_arg_type(struct bpf_verifier_env *env, struct bpf_call_arg_meta *meta,
> >                         return -EINVAL;
> >                 }
> >                 proto->arg_size[arg] = type_size;
> > -               arg_type = ARG_PTR_TO_MEM | MEM_FIXED_SIZE | MEM_WRITE;
> > +               arg_type = ARG_PTR_TO_MEM | MEM_FIXED_SIZE |
> > +                          kfunc_arg_mem_flag(meta->btf, &args[arg]);
> >         }
> >
> >         if (is_kfunc_arg_uninit(meta->btf, &args[arg]))
> > --
> > 2.43.0
> >

  reply	other threads:[~2026-11-06 13:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 10:23 [PATCHv3 bpf-next 0/8] bpf: Add user memory kfuncs Jiri Olsa
2026-11-05 10:23 ` [PATCHv3 bpf-next 1/8] bpf: Honor const on generic kfunc memory arguments Jiri Olsa
2026-11-05 10:59   ` bot+bpf-ci
2026-11-06  0:34   ` Andrii Nakryiko
2026-11-06 13:52     ` Jiri Olsa [this message]
2026-11-06 19:51       ` Andrii Nakryiko
2026-11-05 10:23 ` [PATCHv3 bpf-next 2/8] bpf: Add user memory kfuncs Jiri Olsa
2026-11-05 10:44   ` sashiko-bot
2026-11-06  0:34   ` Andrii Nakryiko
2026-11-06 13:52     ` Jiri Olsa
2026-11-05 10:23 ` [PATCHv3 bpf-next 3/8] selftests/bpf: Add get_procmap_info helper Jiri Olsa
2026-11-05 10:23 ` [PATCHv3 bpf-next 4/8] selftests/bpf: Test const kfunc memory arguments Jiri Olsa
2026-11-05 10:32   ` sashiko-bot
2026-11-05 10:23 ` [PATCHv3 bpf-next 5/8] selftests/bpf: Test user memory mmap kfuncs Jiri Olsa
2026-11-05 10:33   ` sashiko-bot
2026-11-05 10:23 ` [PATCHv3 bpf-next 6/8] selftests/bpf: Test user memory page exec Jiri Olsa
2026-11-05 10:23 ` [PATCHv3 bpf-next 7/8] selftests/bpf: Test bpf_copy_to_user kfunc Jiri Olsa
2026-11-05 10:23 ` [PATCHv3 bpf-next 8/8] selftests/bpf: Test user memory kfunc errors Jiri Olsa
2026-11-06  2:50 ` [PATCHv3 bpf-next 0/8] bpf: Add user memory kfuncs patchwork-bot+netdevbpf

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=au3brpNZG2nANnha@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=memxor@gmail.com \
    --cc=nierro92@gmail.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 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.