[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYIwpHXkqBkMB8zl@bombadil.infradead.org>
Date: Tue, 19 Dec 2023 16:09:08 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Julia Lawall <julia.lawall@...ia.fr>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
Joel Granados <j.granados@...sung.com>,
Dan Carpenter <dan.carpenter@...aro.org>,
Kees Cook <keescook@...omium.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 00/18] sysctl: constify sysctl ctl_tables
On Tue, Dec 19, 2023 at 10:21:25PM +0100, Julia Lawall wrote:
> > As I noted, I think this is a generically neat endeavor and so I think
> > it would be nice to shorthand *any* member of the struct. ctl->any.
> > Julia, is that possible?
>
> What do you mean by *any* member?
I meant when any code tries to assign a new variable to any of the
members of the struct ctl_table *foo, so any foo->*any*
> If any is an identifier typed
> metavariable then that would get any immediate member. But maybe you want
> something like
>
> <+...ctl->any...+>
>
> that will match anything that has ctl->any as a subexpression?
If as just an expression, then no, we really want this to be tied to
the data struture in question we want to modify.
Luis
Powered by blists - more mailing lists