Date: Sat, 2 May 2015 19:21:17 -0700
From: Josh Triplett <josh@joshtriplett.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Iulia Manda <iulia.manda21@gmail.com>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linux Memory Management List <linux-mm@kvack.org>, LKP <lkp@01.org>,
        linux-kernel@vger.kernel.org
Subject: Re: [CONFIG_MULTIUSER] init: error.c:320: Assertion failed in
 nih_error_get: CURRENT_CONTEXT->error != NULL
Message-ID: <20150503022117.GA25173@x>
References: <20150428004320.GA19623@wfg-t540p.sh.intel.com>
 <20150502231828.GA25301@wfg-t540p.sh.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150502231828.GA25301@wfg-t540p.sh.intel.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 898
Lines: 21

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/