From: Dave Chinner <david@fromorbit.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: John Garry <john.g.garry@oracle.com>,
tj@kernel.org, jiangshanlai@gmail.com, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com, jack@suse.cz,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: workqueue lockup debug
Date: Fri, 8 Nov 2024 09:57:38 +1100 [thread overview]
Message-ID: <Zy1F4n9KoNybBmoD@dread.disaster.area> (raw)
In-Reply-To: <4e58d34a-ce45-437a-95a2-3ba21f35bbb5@leemhuis.info>
On Thu, Nov 07, 2024 at 01:39:39PM +0100, Thorsten Leemhuis wrote:
> On 24.10.24 17:49, John Garry wrote:
> > Hi workqueue and scheduler maintainers,
> >
> > As reported in https://lore.kernel.org/linux-fsdevel/df9db1ce-17d9-49f1-
> > ab6d-7ed9a4f1f9c0@oracle.com/T/
> > #m506b9edb1340cdddd87c6d14d20222ca8d7e8796, I am experiencing a
> > workqueue lockup for v6.12-rcX.
>
> John, what this resolved in between? This and the other thread[1] look
> stalled, but I might be missing something. Asking, because I have this
> on my list of tracked regressions and wonder if this is something that
> better should be solved one way or another before 6.12.
>
> [1]
> https://lore.kernel.org/lkml/63d6ceeb-a22f-4dee-bc9d-8687ce4c7355@oracle.com/
I'm still seeing the scheduler bug in -rc6.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-11-07 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 15:49 workqueue lockup debug John Garry
2024-10-24 18:56 ` Tejun Heo
2024-10-25 9:28 ` John Garry
2024-10-29 4:11 ` Dave Chinner
2024-10-29 8:07 ` John Garry
2024-10-29 15:51 ` John Garry
2024-11-07 12:39 ` Thorsten Leemhuis
2024-11-07 22:57 ` Dave Chinner [this message]
2024-11-08 8:54 ` Peter Zijlstra
2024-11-11 13:22 ` John Garry
2024-11-11 21:01 ` Dave Chinner
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=Zy1F4n9KoNybBmoD@dread.disaster.area \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jiangshanlai@gmail.com \
--cc=john.g.garry@oracle.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=regressions@leemhuis.info \
--cc=tj@kernel.org \
/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.