[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANikGpf0OmGMSkksH_ihW9_yXVAL25xKD4CBy8d1gpKj0inPjQ@mail.gmail.com>
Date: Tue, 27 Aug 2024 16:49:04 -0700
From: Juefei Pu <juefei.pu@...il.ucr.edu>
To: James.Bottomley@...senpartnership.com, martin.petersen@...cle.com,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Yu Hao <yhao016@....edu>
Subject: BUG: kernel panic: corrupted stack end in worker_thread
Hello,
We found the following issue using syzkaller on Linux v6.10.
The PoC generated by Syzkaller can have the kernel panic.
The full report including the Syzkaller reproducer:
https://gist.github.com/TomAPU/a96f6ccff8be688eb2870a71ef4d035d
The brief report is below:
Syzkaller hit 'kernel panic: corrupted stack end in worker_thread' bug.
Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 5818 Comm: kworker/0:4 Not tainted 6.10.0 #13
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: 0x0 (ata_sff)
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x23d/0x360 lib/dump_stack.c:114
panic+0x331/0x850 kernel/panic.c:347
schedule_debug+0x2a8/0x3f0 kernel/sched/core.c:5964
__schedule+0x12b/0x15e0 kernel/sched/core.c:6630
__schedule_loop kernel/sched/core.c:6825 [inline]
schedule+0x143/0x310 kernel/sched/core.c:6840
worker_thread+0xc6b/0x1020 kernel/workqueue.c:3424
kthread+0x2eb/0x380 kernel/kthread.c:389
ret_from_fork+0x49/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
Powered by blists - more mailing lists