linux-kernel - Re: [PATCH 00/12] [v2] Reorganize x86 Kconfig menu

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] [day] [month] [year] [list]

Message-ID: <52D5B649.9050103@sr71.net>
Date:	Tue, 14 Jan 2014 14:12:25 -0800
From:	Dave Hansen <dave@...1.net>
To:	Borislav Petkov <bp@...en8.de>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH 00/12] [v2] Reorganize x86 Kconfig menu

On 01/14/2014 06:25 AM, Borislav Petkov wrote:
> On Mon, Jan 13, 2014 at 11:22:45AM -0800, Dave Hansen wrote:
> * CONFIG_X86_X2APIC could go into "Processor Options and Features"
> 
> * We should put "Processor family (...) --->" into the main menu since
> it is one of the most important ones.
> 
> * "Preemption Model" could be merged with "x86 Scheduler Options"
> 
> * Move CONFIG_SECCOMP, CONFIG_COMPAT_VDSO to obscure options?

I actually axed SECCOMP in another set of (arch-independent) patches.

> * Move CONFIG_PHYSICAL_START to "Memory and NUMA Options"
>
> * Maybe group CONFIG_RELOCATABLE, CONFIG_CC_STACKPROTECTOR,
>  CONFIG_PHYSICAL_ALIGN to a separate "Kernel image options" menu.

This is used in concert with a few of the crash dump options, so I think
it makes sense to keep them grouped together.

> * CONFIG_CMDLINE_BOOL - I don't know about this one, it certainly
> doesn't fit anywhere..
> 
> Anyway, just a couple of suggestions

Yup, thanks!  Those are all good suggestions.  I'll definitely take a
look at doing this in the next round.  My focus at this point is to get
this set merged before I accrue too large of a pile.
--
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/