[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <zljx4swb6eyhf67kwm32gcfboedxvikige3p5c7kt5lqo6c2jj@jjoa4g6375re>
Date: Tue, 13 May 2025 17:37:11 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: linux-kernel@...r.kernel.org, Luis Chamberlain <mcgrof@...nel.org>,
Petr Pavlu <petr.pavlu@...e.com>, Sami Tolvanen <samitolvanen@...gle.com>,
Daniel Gomez <da.gomez@...sung.com>, linux-modules@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>, Jason Baron <jbaron@...mai.com>,
Steven Rostedt <rostedt@...dmis.org>, Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH v2] params: Add support for static keys
On Tue, May 13, 2025 at 07:34:59PM -0400, Kent Overstreet wrote:
> On Tue, May 13, 2025 at 02:24:46PM -0700, Josh Poimboeuf wrote:
> > > +++ b/include/linux/moduleparam.h
> > > @@ -122,6 +122,7 @@ struct kparam_array
> > > * charp: a character pointer
> > > * bool: a bool, values 0/1, y/n, Y/N.
> > > * invbool: the above, only sense-reversed (N = true).
> > > + * static_key_t: same as bool, but updates a 'struct static_key'
> >
> > The static_key_*() interfaces are deprecated because they're really easy
> > to use incorrectly. I don't think we want to propagate that misuse to
> > modules.
> >
> > It would be better to have type(s) based on static_key_false and/or
> > static_key_true, depending on whatever the default is.
>
> Except those are just wrappers around struct static_key, so why does
> that matter here?
Those struct wrappers are needed to work with static_branch_likely() and
static_branch_unlikely().
We really need to get rid of old static_key_true() and
static_key_false(), they don't have many users left at this point.
--
Josh
Powered by blists - more mailing lists