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: <CA+55aFx0rLqQUig9VHsfckRX650H=kq6hXH35m=yev17zfi0EA@mail.gmail.com>
Date:	Mon, 15 Jul 2013 10:46:17 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: CONFIG_* used by user-space to figure out whether a feature is on/off

On Mon, Jul 15, 2013 at 10:24 AM, Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
>
> If life was that simple.. This particular issue was with inhibiting certain
> config stanzas if certain features were not built in the kernel. Here is the
> bug that started it:
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633127

Can somebody please open a grub/xen ticket that says all of this is
just too confusing and broken, and that it should just be removed
entirely instead of expanded upon?

This is a grub bug. It really is that simple. Treat it as one.

I don't want to break user space applications, but this isn't a
"user-space app". This is "broken kernel support", and when that
happens, we call them out for being buggy and don't support them
(example: all the gcc bugs that have caused us problems over the
years).

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