[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZCJJwDij0mLB0gwb@codewreck.org>
Date: Tue, 28 Mar 2023 10:58:24 +0900
From: asmadeus@...ewreck.org
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: lucho@...kov.net, Pankaj Raghav <p.raghav@...sung.com>,
Eric Van Hensbergen <ericvh@...il.com>,
Amir Goldstein <amir73il@...il.com>,
Jeff Layton <jlayton@...nel.org>,
Josef Bacik <josef@...icpanda.com>,
linux-kernel@...r.kernel.org, v9fs-developer@...ts.sourceforge.net
Subject: Re: [V9fs-developer] 9p regression linux-next next-20230327
asmadeus@...ewreck.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
Powered by blists - more mailing lists