From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: David Howells <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 <sfr@canb.auug.org.au>
Subject: Re: Regression in next with filesystem context concept
Date: Fri, 7 Sep 2018 19:35:57 +0200 [thread overview]
Message-ID: <20180907193522.1a98d410@aktux> (raw)
In-Reply-To: <20180907161023.GF5662@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]
Hi,
On Fri, 7 Sep 2018 09:10:23 -0700
Tony Lindgren <tony@atomide.com> wrote:
> * David Howells <dhowells@redhat.com> [180907 08:51]:
> > 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.
>
> BTW, I don't think this issue shows up with ramdisk either,
> so that's probably why for example kernelci.org does not
> show errors.
>
I have also similar experience with my automated tests (automated
alarming does not work yet ;-)), I am still in the beginning.
I do there a ramdisk boot to create an overlay mount with the fresh
modules on top of an ordinary rootfs. initramfs mount is
ok, but the microsd card fails.
Testing from a ramdisk I get:
/ # ls -l /dev/mmcblk0p2
brw------- 1 0 0 179, 2 Jan 1 1970 /dev/mmcblk0p2
/ # mount /dev/mmcblk0p2 /mnt/
[ 682.819061] Filesystem requires source device
[ 682.825103] Filesystem requires source device
[ 682.830810] Filesystem requires source device
[ 682.836303] Filesystem requires source device
[ 682.843078] Filesystem requires source device
[ 682.847991] Filesystem requires source device
[ 682.853149] Filesystem requires source device
mount: mounting /dev/mmcblk0p2 on /mnt/ failed: No such file or directory
64GB microsd at omap_hsmmc correcly recognized.
Last known successful boot: next-20180830
so you are not alone with such problems.
will investigate further
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-07 22:18 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 [this message]
2018-09-08 15:24 ` David Howells
2018-09-10 16:08 ` Tony Lindgren
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=20180907193522.1a98d410@aktux \
--to=andreas@kemnade.info \
--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 \
--cc=tony@atomide.com \
/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).