linux-kernel - Re: x86 (Linux Tiny): configure out support for some processors

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.DEB.1.10.0901020849180.20509@asgard.lang.hm>
Date:	Fri, 2 Jan 2009 08:51:28 -0800 (PST)
From:	david@...g.hm
To:	Valdis.Kletnieks@...edu
cc:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Bryan Donlan <bdonlan@...il.com>,
	Ingo Brueckl <ib@...peronline.de>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors

On Fri, 2 Jan 2009, Valdis.Kletnieks@...edu wrote:

> On Fri, 02 Jan 2009 20:40:16 +0530, Jaswinder Singh Rajput said:
>
>> If I know what is my CPU there is no point for supporting all related
>> CPUs in my kernel.
>
> EMBEDDED is for a large assortment of things, all of which are of the form:
>
> General users won't want to change Y, but if I know I don't need Y, there is
> no point in supporting Y in the kernel.
>
> Y might be "this kernel doesn't need sysctl"
> Y might be "support for hot-plug"
> Y might be "printk"
> Y might be "support generic CPUs"
>
> See the pattern?
>
> Yes, we probably could have come up with a better name than EMBEDDED for
> that list of optionals.
>
> CONFIG_TRAINED_TECHNICIANS_ONLY_NO_USER_SERVICABLE_PARTS_INSIDE maybe?

having things outside of the embedded menu depend on embedded makes it 
hard for people to figure out what they need to do to disable specific 
things.

namespaces are also required if ! embedded, but namespaces are not (yet at 
least) something that is commonly used.

if you follow the logic you are providing to it's logical conclusion you 
may as well put all kernel config options under "I really know what I'm 
doing" top level lockout

David Lang
--
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/