linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Regression in next with filesystem context concept
Date: Mon, 10 Sep 2018 09:08:36 -0700	[thread overview]
Message-ID: <20180910160836.GT5662@atomide.com> (raw)
In-Reply-To: <11959.1536420266@warthog.procyon.org.uk>

* David Howells <dhowells@redhat.com> [180908 15:28]:
> Tony Lindgren <tony@atomide.com> 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.

OK thanks for tracking that down, next-20180910 boots again
for me.

Regards,

Tony

  reply	other threads:[~2018-09-10 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 16:43 Regression in next with filesystem context concept Tony Lindgren
2018-09-06 18:11 ` Naresh Kamboju
2018-09-07  8:47 ` David Howells
2018-09-07 16:10   ` Tony Lindgren
2018-09-07 17:35     ` Andreas Kemnade
2018-09-08 15:24   ` David Howells
2018-09-10 16:08     ` Tony Lindgren [this message]
2018-09-10 18:31       ` Guenter Roeck
2018-09-10 19:26         ` Tony Lindgren
2018-09-10 19:32           ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180910160836.GT5662@atomide.com \
    --to=tony@atomide.com \
    --cc=dhowells@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).