linux-kernel - Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP

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:	Mon, 5 May 2008 20:42:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Parag Warudkar <parag.warudkar@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"akpm@...l.org" <akpm@...l.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED

* Sam Ravnborg <sam@...nborg.org> wrote:

> > This is a many years old kconfig bug that is frequently hacked 
> > around in distro kernel packages but which has been ignored upstream 
> > - i've attached Fedora's nonint_oldconfig patch from Dave Jones 
> > below. (maybe Arjan wrote it originally?)
> 
> In latest kbuild.git I've added a new feature.
> 
> 	make K=.config alldefconfig
> 
> would give you eaxtly what you request here. K= is used to say where 
> to locate the base-configuration.

great, thanks Sam!

( how hard would it be to fix the "make oldconfig < /dev/null" infinit 
  loop bug btw? I've got this method in a number of scripts of mine and 
  it's an intuitive thing to type anyway, i think users would like it if 
  it Just Worked. )

> redhat has the added possibility to list new symbols.
> This is not yet included in mainline.
> Not that it is difficult - I just need to decide where/how to do it.

the idea of that is this: distro maintainers dont just want to accept 
new options blindly, they want to make a conscious decision on what 
default to use. So the Fedora rpm builds will bail out with an error if 
a config option has not been provided with a default by the pre-cooked 
configs that are in the SRPM.

In practice distro maintainers will pick the upstream default 99% of the 
time, this is a mechanism to be 'aware' of what is happening upstream, 
via a non-interactive build method. Would be cool to merge this feature 
upstream too, in a clean way.

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