From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:44942 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726314AbeIHUKh (ORCPT ); Sat, 8 Sep 2018 16:10:37 -0400 From: David Howells In-Reply-To: <20180907161023.GF5662@atomide.com> References: <20180907161023.GF5662@atomide.com> <20180906164358.GI5659@atomide.com> <9053.1536310046@warthog.procyon.org.uk> To: Tony Lindgren Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Stephen Rothwell Subject: Re: Regression in next with filesystem context concept MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11958.1536420266.1@warthog.procyon.org.uk> Date: Sat, 08 Sep 2018 16:24:26 +0100 Message-ID: <11959.1536420266@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Tony Lindgren wrote: > > > Looks like next-20180906 now has a regression where mounting > > > root won't work with commit fd0002870b45 ("vfs: Implement a > > > filesystem superblock creation/configuration context"). > > > > Am I right in thinking you're not using any of the LSMs? > > Assuming LSM as in Documentation/lsm.txt, right not using any. The default return value for security_fs_context_parse_param() should be -ENOPARAM, both in security.h and security.c. I've fixed my tree and Al has pulled it, but we're now waiting on Stephen Rothwell to refresh linux/next. David