linux-kernel - Re: [PATCH] transitional config CONFIG_GENERIC

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]

Message-ID: <alpine.LFD.2.00.1005261708420.2995@localhost.localdomain>
Date:	Wed, 26 May 2010 17:13:55 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Christoph Egger <siccegge@...fau.de>
cc:	Ralf Baechle <ralf@...ux-mips.org>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	Jon Hunter <jon-hunter@...com>, linux-kernel@...r.kernel.org,
	vamos@...informatik.uni-erlangen.de
Subject: Re: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS

On Wed, 26 May 2010, Christoph Egger wrote:

> On Wed, May 26, 2010 at 03:56:09PM +0200, Thomas Gleixner wrote:
> > On Wed, 26 May 2010, Christoph Egger wrote:
> > 
> > > Hi all!
> > > 
> > > 	As part of the VAMOS[0] research project at the University of
> > > Erlangen we are looking at multiple integrity errors in linux'
> > > configuration system.
> > > 
> > > 	This was an aid for a transition finished 2007 so not
> > > necessary for some time now, ready for removal.
> > > 
> > > 	Please keep me informed of this patch getting confirmed /
> > > merged so we can keep track of it.
> > 
> > It's still necessary/helpful for any arch which is not yet
> > converted. And there are a few unfortunately.
> 
> 	Are you referring to some out-of-tree architectures? I've
> verified the string GENERIC_CLOCKEVENTS_MIGR is only appearing at this
> single spot in kconfig and nowhere else in code/Kconfig in my
> up-to-date linux tree.

No. I'm referring to in tree archs which do not use the clock events
at all yet. The MIGR symbol allows them to do a step by step
conversion which builds the generic clock events stuff first before
switching over to use them. That's why it was created in the first
place and it has been proven useful when doing such work. So I'd
rather see it stay until all archs actually use the generic framework.

But yes, we can apply your patch and just let them select
GENERIC_CLOCKEVENTS_BUILD instead.

Thanks,

	tglx
--
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/