From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemb@google.com>
Cc: Kuniyuki Iwashima <kuniyu@google.com>,
edumazet@google.com, fw@strlen.de, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: deadlocks on pernet_ops_rwsem
Date: Wed, 1 Oct 2025 13:30:37 -0700 [thread overview]
Message-ID: <20251001133037.0ab6952c@kernel.org> (raw)
In-Reply-To: <CA+FuTSfnOzbZrztVYX26M6xAd5Y-hP0=Ek7svJpDUSLKApK0aQ@mail.gmail.com>
On Wed, 1 Oct 2025 15:33:56 -0400 Willem de Bruijn wrote:
> > > Was there any update on packages (especially qemu?) used by
> > > CI around 2025-09-18 ?
> >
> > No updates according to the logs. First hit was on Thursday so I thought
> > maybe it came from Linus. But looking at the branches we fast forwarded
> > 2025-09-18--21-00 and there were 2 hits earlier that day (2025-09-18--03-00,
> > 2025-09-18--15-00)
>
> Is there a good SHA1 around the time of the earliest report?
>
> There do not seem to be any recent changes to rwsem, let alone
> specifically to pernet_ops_rwsem.
The first time it triggered when net-next was at 152ba35c04ad
and net at 09847108971a, CI branch contents:
https://netdev.bots.linux.dev/static/nipa/branch_deltas/net-next-2025-09-18--03-00.html
The previous one (so the branch before the first time it triggered)
had base commits of 6b957c0a36f5 09847108971a.
If you click on the link above you can go back / forward in the branch
contents.
prev parent reply other threads:[~2025-10-01 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 15:20 deadlocks on pernet_ops_rwsem Jakub Kicinski
2025-10-01 16:46 ` Paolo Abeni
2025-10-01 17:22 ` Jakub Kicinski
2025-10-01 18:50 ` Kuniyuki Iwashima
2025-10-01 19:26 ` Jakub Kicinski
2025-10-01 19:33 ` Willem de Bruijn
2025-10-01 20:30 ` Jakub Kicinski [this message]
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=20251001133037.0ab6952c@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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;
as well as URLs for NNTP newsgroup(s).