From: Guoyu Yin <y04609127@gmail.com>
To: anna-maria@linutronix.de
Cc: frederic@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: [BUG] INFO: rcu detected stall in sys_io_submit
Date: Mon, 19 May 2025 12:39:44 +0800 [thread overview]
Message-ID: <CAJNGr6u38oVsWeh57rmW15H80DpPrd0CH0uLH5kff1W0v6SHLw@mail.gmail.com> (raw)
Hi,
I discovered a kernel crash using the Syzkaller framework, described
as "INFO: rcu detected stall in sys_io_submit". This issue occurs
during the execution of the sys_io_submit system call, where RCU
detects a stall on CPU 3.
From the dmesg log, CPU 3 is stuck in the enqueue_hrtimer function
(kernel/time/hrtimer.c:1085) while handling an hrtimer interrupt.
Meanwhile, the task syz-executor.1 is stuck in memory management
functions (e.g., unmap_mapping_pages, mm/memory.c:3849) during
sys_io_submit execution. This likely causes the RCU stall.
I suspect this is due to delays in hrtimer processing or prolonged
blocking in memory management operations. I recommend reviewing the
enqueue_hrtimer implementation and the interaction between
sys_io_submit, AIO, and the EXT4 filesystem.
The full dmesg log is attached. Please feel free to contact me for
additional information or reproduction steps.
This can be reproduced on:
HEAD commit:
fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
report: https://pastebin.com/raw/D6PmW878
console output : https://pastebin.com/raw/qeLqJsRF
kernel config: https://pastebin.com/raw/zrj9jd1V
C reproducer : https://pastebin.com/raw/EprKHENh
Best regards,
Guoyu
reply other threads:[~2025-05-19 4:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJNGr6u38oVsWeh57rmW15H80DpPrd0CH0uLH5kff1W0v6SHLw@mail.gmail.com \
--to=y04609127@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
/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