From: Corey Minyard <minyard@acm.org>
To: Juergen Gross <jgross@suse.com>
Cc: Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Possible reproduction of CSD locking issue
Date: Wed, 26 Jan 2022 09:31:17 -0600 [thread overview]
Message-ID: <20220126153117.GU34919@minyard.net> (raw)
In-Reply-To: <70245998-b99e-ebe7-e932-f8a1b46f6ac7@suse.com>
On Wed, Jan 26, 2022 at 03:51:36PM +0100, Juergen Gross wrote:
> On 26.01.22 14:56, Corey Minyard wrote:
> > On Wed, Jan 26, 2022 at 07:08:22AM +0100, Juergen Gross wrote:
snip..
> >
> > csd: cnt(63d8e1f): 0003->0037 queue
> > csd: cnt(63d8e20): 0003->0037 ipi
> > csd: cnt(63d8e21): 0003->0037 ping
> >
> > In __smp_call_single_queue_debug CPU 3 sends another message to
> > CPU 55 and sends an IPI. But there should be a pinged entry
> > after this.
> >
> > csd: cnt(63d8e22): 0003->0037 queue
> > csd: cnt(63d8e23): 0003->0037 noipi
>
> This is interesting. Those are 5 consecutive entries without any
> missing in between (see the counter values). Could it be that after
> the ping there was an interrupt and the code was re-entered for
> sending another IPI? This would clearly result in a hang as seen.
Since preempt is enabled, wouldn't it eventually come back to the first
thread and send the IPI? Unless CPU 3 is stuck in an interrupt or
interrupt storm.
-corey
next prev parent reply other threads:[~2022-01-26 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 18:27 Possible reproduction of CSD locking issue Corey Minyard
2022-01-25 18:53 ` Paul E. McKenney
2022-01-25 21:52 ` Corey Minyard
2022-01-25 22:51 ` Paul E. McKenney
2022-01-26 6:08 ` Juergen Gross
2022-01-26 13:56 ` Corey Minyard
2022-01-26 14:12 ` Corey Minyard
2022-01-26 14:51 ` Juergen Gross
2022-01-26 15:31 ` Corey Minyard [this message]
2022-01-26 15:34 ` Juergen Gross
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=20220126153117.GU34919@minyard.net \
--to=minyard@acm.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox