From: Dominique Martinet <asmadeus@codewreck.org>
To: Jakub Kicinski <kuba@kernel.org>, Mateusz Guzik <mjguzik@gmail.com>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
v9fs@lists.linux.dev
Subject: Re: hangs after merge window changes
Date: Thu, 18 Jul 2024 10:14:57 +0900 [thread overview]
Message-ID: <ZphskWZb_pkxMVvW@codewreck.org> (raw)
In-Reply-To: <20240717163051.13e41526@kernel.org>
Jakub Kicinski wrote on Wed, Jul 17, 2024 at 04:30:51PM -0700:
> On Thu, 18 Jul 2024 05:45:18 +0900 Dominique Martinet wrote:
> > Eric Van Hensbergen wrote on Wed, Jul 17, 2024 at 01:01:26PM -0500:
> > > I held way back on adding anything new over the past cycle, so this
> > > sounds likely some external change maybe perturbing an older issue.
> > > What guest side mount options, qemu options and qemu version are you
> > > using?
> >
> > Mount option if any would be much appreciated, yes.
> > Also, what version you upgraded from to limit the limit the search a
> > bit; the previous 6.9 tree?
>
> Between networking pull requests. Basically
> 528dd46d0fc35c0176257a13a27d41e44fcc6cb3 to
> 51835949dda3783d4639cfa74ce13a3c9829de00
Thanks, this includes this commit:
7180f8d91fcb ("vfs: add rcu-based find_inode variants for iget ops")
I think that's our most likely candidate at this point, adding Mateusz
and others involved in Cc until I find more time to reproduce.
@Mateusz, Jan, Christian - sorry if it wasn't the culprit.
We're seeing new hangs in find_inode_fast between the above two commits,
see the extact hang traces top of the original mail:
https://lore.kernel.org/v9fs/CAFkjPTnTDWrfCSVzvtSszjoerOeWBn8Z6DC4qFMH70Aq7Pqr1Q@mail.gmail.com/T/#t
> > Also couldn't find much infos about the CI in general, given the traces
> > I don't think the workload matters all that much but it can give
> > something to start with e.g. running from initrd and mounting 9p or
> > using 9p as rootfs; that shouldn't make a difference but might as well
> > try to reproduce from something close to the actual netdev CI given the
> > low reproducibility.
>
> What CI does is described here:
> https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
> it's fairly simple, virtme-ng just runs kselftests inside a VM with
> the host FS mounted via 9p-virtio.
>
> I'd offer running experiments on the exact systems, but this week
> I'm partially AFK (at a conference).
Thanks.
You're not doing anything specific, I'll hopefully be able to reproduce
it running similar workloads at which point I'll try to improve the
reproducer and get a closer look if Mateusz or others didn't beat me to
it.
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2024-07-18 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 17:24 hangs after merge window changes Jakub Kicinski
2024-07-17 18:01 ` Eric Van Hensbergen
2024-07-17 20:45 ` Dominique Martinet
2024-07-17 23:30 ` Jakub Kicinski
2024-07-18 1:14 ` Dominique Martinet [this message]
2024-07-18 3:54 ` Mateusz Guzik
2024-07-18 4:08 ` Mateusz Guzik
2024-07-18 10:42 ` Jan Kara
2024-07-18 10:57 ` Mateusz Guzik
2024-07-18 11:40 ` Mateusz Guzik
2024-07-18 12:16 ` Jan Kara
2024-07-18 12:29 ` Mateusz Guzik
2024-07-17 21:42 ` Jakub Kicinski
2024-07-17 22:00 ` 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=ZphskWZb_pkxMVvW@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=ericvh@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=mjguzik@gmail.com \
--cc=v9fs@lists.linux.dev \
/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