[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240206122857.svm2ptz2hsvk4sco@quack3>
Date: Tue, 6 Feb 2024 13:28:57 +0100
From: Jan Kara <jack@...e.cz>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Jan Kara <jack@...e.cz>, linux-block <linux-block@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
linux-fsdevel@...r.kernel.org, lkft-triage@...ts.linaro.org,
Arnd Bergmann <arnd@...db.de>,
Christian Brauner <brauner@...nel.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: next: /dev/root: Can't open blockdev
On Tue 06-02-24 15:53:34, Naresh Kamboju wrote:
> On Tue, 6 Feb 2024 at 15:45, Jan Kara <jack@...e.cz> wrote:
> >
> > On Tue 06-02-24 14:41:17, Naresh Kamboju wrote:
> > > All qemu's mount rootfs failed on Linux next-20230206 tag due to the following
> > > kernel crash.
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> > >
> > > Crash log:
> > > ---------
> > > <3>[ 3.257960] /dev/root: Can't open blockdev
> > > <4>[ 3.258940] VFS: Cannot open root device "/dev/sda" or
> > > unknown-block(8,0): error -16
> >
> > Uhuh, -16 is EBUSY so it seems Christian's block device opening changes are
> > suspect? Do you have some sample kconfig available somewhere?
>
> All build information is in this url,
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2byqguFVp7MYAEjKo6nJGba2FcP/
Thanks! So for record the config has:
CONFIG_BLK_DEV_WRITE_MOUNTED=y
So we are not hitting any weird corner case with blocking writes to mounted
filesystems. It must be something else.
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists