linux-kernel - Re: [CONFIG_MULTIUSER] init: error.c:320: Assertion failed in nih_error_get: CURRENT

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: <20150503022117.GA25173@x>
Date:	Sat, 2 May 2015 19:21:17 -0700
From:	Josh Triplett <josh@...htriplett.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Iulia Manda <iulia.manda21@...il.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Memory Management List <linux-mm@...ck.org>,
	LKP <lkp@...org>, linux-kernel@...r.kernel.org
Subject: Re: [CONFIG_MULTIUSER] init: error.c:320: Assertion failed in
 nih_error_get: CURRENT_CONTEXT->error != NULL

On Sun, May 03, 2015 at 07:18:28AM +0800, Fengguang Wu wrote:
> Hi Iulia,
> 
> FYI, there are Ubuntu init error messages when CONFIG_MULTIUSER=n.
> Since it's not embedded system and hence the target user of
> CONFIG_MULTIUSER=n, it might be fine..

I would expect a non-trivial amount of work required to make a standard
distribution boot with CONFIG_MULTIUSER=n.  Anything attempting to set
the user ID or group ID will fail, such as su, start-stop-daemon
--chuid, or systemd's daemon launching code.

So I'd suggest that this is an expected failure; allnoconfig or
tinyconfig would already not be expected to boot unmodified Ubuntu.

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