[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11178040.rrurhZOAV8@blindfold>
Date: Thu, 21 Mar 2019 17:34:40 +0100
From: Richard Weinberger <richard@....at>
To: David Howells <dhowells@...hat.com>
Cc: viro@...iv.linux.org.uk, linux-block@...r.kernel.org,
squashfs-devel@...ts.sourceforge.net,
Marek Vasut <marek.vasut@...il.com>,
Brian Norris <computersforpeace@...il.com>,
Nicolas Pitre <nico@...aro.org>,
Boris Brezillon <bbrezillon@...nel.org>,
linux-mtd@...ts.infradead.org,
David Woodhouse <dwmw2@...radead.org>,
Phillip Lougher <phillip@...ashfs.org.uk>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/6] Convert mount_single-using filesystems to fs_context
Am Donnerstag, 21. März 2019, 16:45:02 CET schrieb David Howells:
> Richard Weinberger <richard@....at> wrote:
>
> > > Bah. The problem is that vfs_get_super() doesn't set fc->root before
> > > calling reconfigure_super().
> >
> > Do you still need the disassembly?
>
> Thanks, but no. I've pushed replacement patches to my git branch.
Just gave it a try, jffs2 does not mount anymore. The problem is that you define
an Opt_source in super.c, but never evaluate it -> jffs2_parse_param() returns
-EINVAL.
What I really don't get is the new logging stuff in include/linux/fs_context.h.
printk() is already an overloaded beat, why another layer?
The log output seems very odd to me:
[ 13.117593] e MTD: Couldn't look up '/dev/mtd0': -15
Please notice the "e" before MTD, first I though this is a memory
corruption, but is your log level?!
Thanks,
//richard
Powered by blists - more mailing lists