linux-kernel - Re: [PATCH] x86: defconfig: Enable CONFIG

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]

Date:	Wed, 26 Nov 2014 10:43:34 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Richard Weinberger <richard@....at>
Cc:	Dave Jones <davej@...hat.com>, x86@...nel.org, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, gregkh@...uxfoundation.org,
	rafael.j.wysocki@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: defconfig: Enable CONFIG_FHANDLE

On Wed, 2014-11-26 at 01:11 +0100, Richard Weinberger wrote:
> Am 26.11.2014 um 00:43 schrieb Dave Jones:
> > On Wed, Nov 26, 2014 at 12:36:52AM +0100, Richard Weinberger wrote:
> >  > systemd has a hard dependency on CONFIG_FHANDLE.
> >  > If you run systemd with CONFIG_FHANDLE=n it will somehow
> >  > boot but fail to spawn a getty or other basic services.
> >  > As systemd is now used by most x86 distributions it
> >  > makes sense to enabled this by default and save kernel
> >  > hackers a lot of value debugging time.
> > 
> > Perhaps also note this in the kconfig entry for it ?
> 
> I'm not sure if this helps a lot.
> But I can create patch (including for all other systemd dependencies).

How would people find these notes: by grepping Kconfig files for
"systemd"? Wouldn't it make more sense - if what Richard states is
correct - to just enable those dependencies by default (provided they
have no adverse effects for a, well, not too big group of x86 systems)?


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/