[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZCI+7Wg5OclSlE8c@bombadil.infradead.org>
Date: Mon, 27 Mar 2023 18:12:13 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: v9fs-developer@...ts.sourceforge.net
Cc: Josef Bacik <josef@...icpanda.com>,
Jeff Layton <jlayton@...nel.org>,
Eric Van Hensbergen <ericvh@...il.com>, lucho@...kov.net,
asmadeus@...ewreck.org, v9fs-developer@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, Pankaj Raghav <p.raghav@...sung.com>,
Amir Goldstein <amir73il@...il.com>
Subject: 9p regression linux-next next-20230327
kdevops uses 9p for its client / host setup to enable rapid kernel
development on guests using the host to compile / guest to install
a read-only-mount.
I updated the kernel today to next-20230327 and see the 9p mount won't
come up and so boot fails. I'm starting to bisect and see next-20230301
was OK. So at least have:
next-20230301: GOOD
next-20230315: GOOD
next-20230327: BAD
Once I narrow this down a bit further I'll poke back.
What sort of tests are run for 9p before some development changes get
pushed into a tree that lands on linux-next? If none exists, simply
testing 'make linux' works with kdevops could perhaps be a start.
Luis
Powered by blists - more mailing lists