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: <1373915638.2591.45.camel@x61.thuisdomein>
Date:	Mon, 15 Jul 2013 21:13:58 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
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, 2013-07-15 at 15:03 -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 08:25:43PM +0200, Paul Bolle wrote:
> > 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.

But, whatever you choose to do in the future, that needn't stop you from
dropping XEN_PRIVILIGED_GUEST now. It's basically a trivial cleanup.


Paul Bolle

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