Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 27 Mar 2023 18:12:13 -0700
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
Message-ID: <ZCI+7Wg5OclSlE8c@bombadil.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: Luis Chamberlain <mcgrof@infradead.org>
Precedence: bulk

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