From: asmadeus@codewreck.org
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: lucho@ionkov.net, Pankaj Raghav <p.raghav@samsung.com>,
Eric Van Hensbergen <ericvh@gmail.com>,
Amir Goldstein <amir73il@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [V9fs-developer] 9p regression linux-next next-20230327
Date: Tue, 28 Mar 2023 10:58:24 +0900 [thread overview]
Message-ID: <ZCJJwDij0mLB0gwb@codewreck.org> (raw)
In-Reply-To: <ZCJGjuOYR6nGXiAw@codewreck.org>
asmadeus@codewreck.org wrote on Tue, Mar 28, 2023 at 10:44:46AM +0900:
> I've just built Eric's for-next branch and I'm not seeing any issue
> there, I'll be checking the next tag you pointed at next.
Well, at the very least I can confirm mount hangs there :)
[<0>] p9_client_rpc+0xf1/0x380 [9pnet]
[<0>] p9_client_attach+0x8d/0x1d0 [9pnet]
[<0>] v9fs_session_init+0x4ad/0x810 [9p]
[<0>] v9fs_mount+0x6a/0x420 [9p]
[<0>] legacy_get_tree+0x28/0x50
[<0>] vfs_get_tree+0x1a/0x90
[<0>] path_mount+0x746/0x9b0
[<0>] __x64_sys_mount+0x153/0x1b0
[<0>] do_syscall_64+0x3c/0x80
[<0>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
And my async flush hasn't gotten fixed yet, so that mount cannot be
killed either.
I can mount over tcp so it's a virtio change, I'll dig a bit more and
report back with you and cc
--
Dominique
next prev parent reply other threads:[~2023-03-28 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 1:12 9p regression linux-next next-20230327 Luis Chamberlain
2023-03-28 1:44 ` asmadeus
2023-03-28 1:58 ` asmadeus [this message]
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=ZCJJwDij0mLB0gwb@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=amir73il@gmail.com \
--cc=ericvh@gmail.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mcgrof@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.