All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Jakub Kicinski <kuba@kernel.org>,
	Eric Van Hensbergen <ericvh@kernel.org>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev
Subject: Re: hangs after merge window changes
Date: Thu, 18 Jul 2024 05:45:18 +0900	[thread overview]
Message-ID: <ZpgtXjz3pbJKUjL7@codewreck.org> (raw)
In-Reply-To: <CAFkjPTnktf6puYAyg4pNh8RtQvSuQnSo5VCQvinv=Cw9m1s9xQ@mail.gmail.com>

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?

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.

> Dominique, you aware of anything coming in that might have messed with
> this?  Maybe the new common code refactoring underpinning
> readahead/etc.?

Given the trace it's probably stuck in __wait_on_freeing_inode (the only
schedule() call in find_inode_fast), so we could be looking at
fallbacks from the iget changes but that made it in 6.9 already so
that's unlikely...

I have a feeling that adding cache will make the error go away if you
just want to fix tests for now, so would be great if you could try
adding -o cache=loose to the 9p mount options; hopefully the inodes
won't be freed as often and that'll make the race harder to hit.


I had a quick look at other globals fs changes and nothing stood out,
it's going to be fun to track down.

> On Wed, Jul 17, 2024 at 12:24 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > Apologies for possible duplicate, I tried to search lore and haven't
> > found anything, but also I can't find the exact 9p archive there :S

The new list is here: https://lore.kernel.org/v9fs/
You probably didn't miss anything :)

-- 
Dominique

  reply	other threads:[~2024-07-17 20:45 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 [this message]
2024-07-17 23:30     ` Jakub Kicinski
2024-07-18  1:14       ` Dominique Martinet
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=ZpgtXjz3pbJKUjL7@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --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 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.