From: Guoyu Yin <y04609127@gmail.com>
To: ericvh@kernel.org
Cc: lucho@ionkov.net, asmadeus@codewreck.org,
linux_oss@crudebyte.com, v9fs@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [BUG] INFO: rcu_tasks_trace detected stalls? (Late IPI?)
Date: Thu, 15 May 2025 15:36:04 +0800 [thread overview]
Message-ID: <CAJNGr6uG6h=dBLjfB5ajZjv4qdf8-LjcW-i8L3_oqhbvBosSuA@mail.gmail.com> (raw)
Hi,
I discovered a kernel crash with the description "INFO:
rcu_tasks_trace detected stalls? (Late IPI?)". Analysis of the logs
suggests that the issue may be related to numerous 9P network file
system connection failures and high system load.
Specifically, the p9_fd_create_tcp function repeatedly fails when
attempting to connect to 127.0.0.1, with the error "problem connecting
socket to 127.0.0.1". This could lead to resource exhaustion,
affecting CPU scheduling and interrupt handling, ultimately triggering
the RCU stall. The logs also show EXT4 file system errors (e.g., block
bitmap inconsistencies and delayed block allocation failures), likely
a side effect of Syzkaller testing.
I recommend investigating the 9P network file system’s connection
logic (particularly the socket connection part in p9_fd_create_tcp)
and system resource usage to pinpoint the root cause of the connection
failures and high load.
This can be reproduced on:
HEAD commit:
38fec10eb60d687e30c8c6b5420d86e8149f7557
report: https://pastebin.com/raw/0LB0VhWw
console output : https://pastebin.com/raw/EtnaHBBq
kernel config : https://pastebin.com/raw/u0Efyj5P
C reproducer : https://pastebin.com/raw/WzZ023uX
reply other threads:[~2025-05-15 7:36 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='CAJNGr6uG6h=dBLjfB5ajZjv4qdf8-LjcW-i8L3_oqhbvBosSuA@mail.gmail.com' \
--to=y04609127@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).