From: Tianyu Li <lty218@stu.pku.edu.cn>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm <linux-mm@kvack.org>, akpm <akpm@linux-foundation.org>,
xujiakai2025 <xujiakai2025@iscas.ac.cn>,
"zhaoruilin22@mails.ucas.ac.cn" <zhaoruilin22@mails.ucas.ac.cn>
Subject: [BUG] Possible Circular Locking Dependency (deadlock) in pcpu_alloc_mutex and might_alloc
Date: Tue, 9 Dec 2025 18:37:40 +0800 (GMT+08:00) [thread overview]
Message-ID: <AN6AuABUJ1wJzL8FhRfI7Koh.1.1765276660708.Hmail.2200013188@stu.pku.edu.cn> (raw)
Hello,
Lockdep reports a possible circular locking dependency (deadlock) detected via a fuzzing framework on Linux 6.18.0-rc7, and it also appears to be reproducible on v6.18. Since the report itself is already quite clear, I don’t want to risk adding inaccurate analysis here. Instead, I have attached the relevant information and materials below for your review.
Kernel source: https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.18.tar.xz
Kernel configuration: https://github.com/j1akai/KConfigFuzz_bug/raw/refs/heads/main/x86/mainline-config
Kernel log(report): https://github.com/Wxm-233/KConfigFuzz_crashes/raw/refs/heads/main/0f85fc661af1e3c69b26b97eaaaa43d629de449c/report0
Reproduction C Code: https://github.com/Wxm-233/KConfigFuzz_crashes/raw/refs/heads/main/0f85fc661af1e3c69b26b97eaaaa43d629de449c/repro.cprog
Syscall sequence for reproduction (more precise): https://github.com/Wxm-233/KConfigFuzz_crashes/raw/refs/heads/main/0f85fc661af1e3c69b26b97eaaaa43d629de449c/repro.prog
GCC info: https://github.com/Wxm-233/KConfigFuzz_crashes/raw/refs/heads/main/0f85fc661af1e3c69b26b97eaaaa43d629de449c/gccinfo
I hope this report helps in identifying and resolving the issue. Thanks for your time and attention.
Best regards.
reply other threads:[~2025-12-09 10:37 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=AN6AuABUJ1wJzL8FhRfI7Koh.1.1765276660708.Hmail.2200013188@stu.pku.edu.cn \
--to=lty218@stu.pku.edu.cn \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xujiakai2025@iscas.ac.cn \
--cc=zhaoruilin22@mails.ucas.ac.cn \
/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