[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YxF4H9MTDj+PnJ+V@kernel.org>
Date: Fri, 2 Sep 2022 06:27:27 +0300
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Roberto Sassu <roberto.sassu@...weicloud.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Mykola Lysenko <mykolal@...com>,
David Howells <dhowells@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>,
"Serge E . Hallyn" <serge@...lyn.com>,
Shuah Khan <shuah@...nel.org>, bpf <bpf@...r.kernel.org>,
keyrings@...r.kernel.org,
LSM List <linux-security-module@...r.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Daniel Müller <deso@...teo.net>,
Kumar Kartikeya Dwivedi <memxor@...il.com>,
Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [PATCH v14 05/12] KEYS: Move KEY_LOOKUP_ to include/linux/key.h
and set KEY_LOOKUP_FLAGS_ALL
On Wed, Aug 31, 2022 at 08:33:38AM -0700, Alexei Starovoitov wrote:
> On Wed, Aug 31, 2022 at 2:24 AM Roberto Sassu
> <roberto.sassu@...weicloud.com> wrote:
> > > > >
> > > > > +#define KEY_LOOKUP_CREATE 0x01
> > > > > +#define KEY_LOOKUP_PARTIAL 0x02
> > > > > +#define KEY_LOOKUP_FLAGS_ALL (KEY_LOOKUP_CREATE |
> > > > > KEY_LOOKUP_PARTIAL)
> > > >
> > > > IMHO this could be just KEY_LOOKUP_ALL.
>
> Since this is supposed to be kernel internal flags
> please make them enum, so that bpf progs can auto-adjust
> (with the help of CORE) to changes in this enum.
> With #define there is no way for bpf prog to know
> when #define changed in the future kernels.
Isn't enum also Rust compatibility requirement, or do I remember
incorrectly? Anyway, good suggestion.
BR, Jarkko
Powered by blists - more mailing lists