linux-kernel - Re: [PATCH v4 2/8] init.h: add __read_mostly to early_param_on

lists.openwall.net		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:	Thu, 30 Apr 2015 20:32:00 +0200
From:	"Luis R. Rodriguez" <mcgrof@...e.com>
To:	Borislav Petkov <bp@...e.de>, Kyle McMartin <kyle@...nel.org>,
	Christoph Lameter <cl@...ux.com>,
	Alok N Kataria <alokk@...softinc.com>,
	Shobhit Dayal <shobhit@...softinc.com>,
	Shai Fultheim <shai@...lex86.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>, mingo@...e.hu,
	tglx@...utronix.de, hpa@...or.com, plagnioj@...osoft.com,
	tomi.valkeinen@...com, daniel.vetter@...el.com, airlied@...ux.ie,
	dledford@...hat.com, awalls@...metrocast.net, syrjala@....fi,
	luto@...capital.net, mst@...hat.com, cocci@...teme.lip6.fr,
	linux-kernel@...r.kernel.org, Juergen Gross <jgross@...e.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Dave Airlie <airlied@...hat.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org
Subject: Re: [PATCH v4 2/8] init.h: add __read_mostly to early_param_on_off()

On Thu, Apr 30, 2015 at 06:00:44PM +0200, Borislav Petkov wrote:
> On Wed, Apr 29, 2015 at 02:44:21PM -0700, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@...e.com>
> 
> So this one is missing a commit message too but we need to talk about
> this. Why are we adding __read_mostly in the macro? This would put every
> param declared this way into __section__(".data..read_mostly") and I'm
> not really convinced that is needed.
> 
> Those setup params get accessed a couple of times only during boot, in
> non-critical paths so we don't really care.
> 
> If you care about pat_enabled being read a lot, you could do:
> 
> int __read_mostly pat_enabled;
> 
> only for it.
> 
> But for every param declared this way? I'm not sure we want that...

I'm glad you bring this up, Christoph can you or anyone else can you provide
advise since you added __read_mostly ?

I added this to early_param_on_off() given I saw a prevalence of __read_mostly
in similar taste elsewhere in the kernel on kernel parameters, and since this
patch tried to convert one kernel parameter which used __read_mostly over to
early_param_on_off() I decided to add it and now we need to really decide if
its ideal for kernel parameters or not.

In this particular case early_param_on_off() will be used for boot time kernel
parameters which we do not intend on dynamically change a lot at run time, we
at run time in early boot have to disable a feature but this will typically
happen only once.

  Luis

> > diff --git a/include/linux/init.h b/include/linux/init.h
> > index 21b6d76..a0385cc 100644
> > --- a/include/linux/init.h
> > +++ b/include/linux/init.h
> > @@ -272,7 +272,7 @@ struct obs_kernel_param {
> >  
> >  #define early_param_on_off(str_on, str_off, var, config)		\
> >  									\
> > -	int var = IS_ENABLED(config);					\
> > +	int __read_mostly var = IS_ENABLED(config);			\
> >  									\
> >  	static int __init parse_##var##_on(char *arg)			\
> >  	{								\
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/