From: Thomas Gleixner <tglx@linutronix.de>
To: 胡焜 <huk23@m.fudan.edu.cn>
Cc: 白烁冉 <baishuoran@hrbeu.edu.cn>,
"Peter Zijlstra" <peterz@infradead.org>,
"jjtan24@m.fudan.edu.cn" <jjtan24@m.fudan.edu.cn>,
linux-kernel@vger.kernel.org
Subject: Re: possible deadlock in smp_call_function_many_cond
Date: Thu, 24 Jul 2025 11:35:59 +0200 [thread overview]
Message-ID: <87o6taq6bk.ffs@tglx> (raw)
In-Reply-To: <C0FEC6BF-BCC8-4301-BBE6-8A49A05D50D6@m.fudan.edu.cn>
On Thu, Jul 24 2025 at 15:55, 胡焜 wrote:
Please do not top-post and trim your replies:
https://people.kernel.org/tglx/notes-about-netiquette
> My guess is that the crash point might be csd_lock_wait(csd) in
> ~/kernel/smp.c on line 885. Here the other CPUs are notified via IPI
> to execute flush_tlb_mm_range and enter spin wait. However, it has not
> yet been determined which CPU performed the operation that caused the
> IPI to return a timeout.
Guessing is not a proper engineering method :)
> I'll first provide the log that was reproduced in 6.16-rc4. we'll re-verify it on rc7.
> [ 0.000000][ T0] Linux version 6.16.0-rc4 (qjj@qjj-Standard-PC-Q35-ICH9-2009) (gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT_DYNAMIC Wed Jul 2 09:53:03 CST 2025
>
> [ 0.000000][ T0] Command line: root=/dev/sda console=ttyS0 ftrace_dump_on_oops hrtimer_expire_entry hrtimer_expire_exit trace_event=ipi_entry,ipi_exit,irq_handler_entry,irq_handler_exit
Please remove the silly extra new-lines next time.
>
> [ 0.427302][ T0] Unknown kernel command line parameters "hrtimer_expire_entry hrtimer_expire_exit spec_store_bypass_disable=prctl nbds_max=32", will be passed to user space.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
How is this helpful?
next prev parent reply other threads:[~2025-07-24 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 14:03 possible deadlock in smp_call_function_many_cond 白烁冉
2025-07-20 19:38 ` Thomas Gleixner
2025-07-21 1:38 ` 胡焜
2025-07-24 7:55 ` 胡焜
2025-07-24 9:35 ` Thomas Gleixner [this message]
[not found] ` <775c18ba.1d7b5.199098fbc3f.Coremail.baishuoran@hrbeu.edu.cn>
[not found] ` <87frcuro62.ffs@tglx>
2025-09-21 13:35 ` Re: " 白烁冉
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=87o6taq6bk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=baishuoran@hrbeu.edu.cn \
--cc=huk23@m.fudan.edu.cn \
--cc=jjtan24@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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