lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 19 Dec 2023 16:09:08 -0800
From: Luis Chamberlain <>
To: Julia Lawall <>
Cc: Thomas WeiƟschuh <>,
	Joel Granados <>,
	Dan Carpenter <>,
	Kees Cook <>,
	"Gustavo A. R. Silva" <>,
	Iurii Zaikin <>,
	Greg Kroah-Hartman <>,,,
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.


Powered by blists - more mailing lists