From: Luis Chamberlain <mcgrof@kernel.org>
To: v9fs-developer@lists.sourceforge.net
Cc: Josef Bacik <josef@toxicpanda.com>,
Jeff Layton <jlayton@kernel.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
lucho@ionkov.net, asmadeus@codewreck.org,
v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Pankaj Raghav <p.raghav@samsung.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: 9p regression linux-next next-20230327
Date: Mon, 27 Mar 2023 18:12:13 -0700 [thread overview]
Message-ID: <ZCI+7Wg5OclSlE8c@bombadil.infradead.org> (raw)
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
next reply other threads:[~2023-03-28 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 1:12 Luis Chamberlain [this message]
2023-03-28 1:44 ` asmadeus
2023-03-28 1:58 ` [V9fs-developer] " asmadeus
2023-03-28 4:46 ` Luis Chamberlain
2023-03-28 14:28 ` Eric Van Hensbergen
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=ZCI+7Wg5OclSlE8c@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=p.raghav@samsung.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®