linux-kernel - [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet

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

Message-Id: <20130701200440.712D8B4E@viggo.jf.intel.com>
Date:	Mon, 01 Jul 2013 13:04:40 -0700
From:	Dave Hansen <dave@...1.net>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, Dave Hansen <dave@...1.net>
Subject: [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet

Linus, I've tried to send these along to a couple of different
maintainers for a couple of merge windows, but so far nobody has
bitten.

--

I think the "Kernel Hacking" menu has gotten a bit out of hand.  It
is over 120 lines long on my system with everything enabled and
options are scattered around it haphazardly.

        http://sr71.net/~dave/linux/kconfig-horror.png

Let's try to introduce some sanity.  This set takes that 120 lines
down to 55 and makes it vastly easier to find some things.  It's a
start.

This set stands on its own, but there is plenty of room for follow-up
patches.  The arch-specific debug options still end up getting stuck
in the top-level "kernel hacking" menu.  OPTIMIZE_INLINING, for
instance, could obviously go in to the "compiler options" menu, but
the fact that it is defined in arch/ in a separate Kconfig file keeps
it on its own for the moment.

--

There is a fair amount of churn in the areas around these patches
so I've resolved conflicts a couple of times.  For the patches that
are almost purely code move patches, I'm doing this:

	cat foo.patch | grep '^[-+]' | perl -pe 's/^.//' | sort | uniq -c | sort -n

and watching for any non-even numbers coming out of uniq.  This
helps me make sure I'm not adding/removing code that I should not
be.

The Signed-off-by's in here look funky.  I changed employers
while working on this set, so I have signoffs from both email
addresses.  Here's the original posting:

	http://lkml.kernel.org/r/20121217182206.91AA150A@kernel.stglabs.ibm.com

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