linux-kernel - Re: CONFIG_* used by user-space to figure out whether a feature is on/off

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: <20130715190311.GA3385@phenom.dumpdata.com>
Date:	Mon, 15 Jul 2013 15:03:11 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michael Opdenacker <michael.opdenacker@...e-electrons.com>
Subject: Re: CONFIG_* used by user-space to figure out whether a feature is
 on/off

On Mon, Jul 15, 2013 at 08:25:43PM +0200, Paul Bolle wrote:
> On Mon, 2013-07-15 at 14:02 -0400, Konrad Rzeszutek Wilk wrote:
> > How about I make you proud and post a patch. See:
> > 
> >  http://article.gmane.org/gmane.comp.boot-loaders.grub.devel/20332 
> 
> And you're now also taking Michael's patch, that triggered this
> discussion, aren't you?

I believe there is a better way of doing this that I had enumerated
in the thread (see "xen: remove unused Kconfig parameter"). That was to
remove the CONFIG_XEN_PRIVILIGED and XEN_CONFIG_DOM0 and instead have an
CONFIG_XEN_HARDWARE_DOMAIN and CONFIG_XEN_CONTROL_DOMAIN which reflect the
reality a lot better.

P.S.
That idea had been percolating a bit - and it started way back with Andrew Jones
proposing an Kconfig patch a year ago - see:
http://lists.xen.org/archives/html/xen-devel/2012-01/msg00500.html for some
backstory.
--
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/