linux-kernel - Re: [syzbot] [riscv?] kernel panic: Kernel stack overflow (2)

Open Source and information security mailing list archives

Message-ID: <035070c6-7adf-4a38-bb5a-fdc4be353c93@ghiti.fr>
Date: Sun, 4 Feb 2024 17:24:54 +0100
From: Alexandre Ghiti <alex@...ti.fr>
To: syzbot <syzbot+5c1ebfe49c5e8e998e75@...kaller.appspotmail.com>,
 aou@...s.berkeley.edu, linux-kernel@...r.kernel.org,
 linux-riscv@...ts.infradead.org, palmer@...belt.com,
 paul.walmsley@...ive.com, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [riscv?] kernel panic: Kernel stack overflow (2)

On 03/02/2024 19:02, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit:    6613476e225e Linux 6.8-rc1
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
> console output: https://syzkaller.appspot.com/x/log.txt?x=144ac160180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=877e61347079aad5
> dashboard link: https://syzkaller.appspot.com/bug?extid=5c1ebfe49c5e8e998e75
> compiler:       riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: riscv64
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10c57b90180000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15d369ffe80000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-6613476e.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/33ea806d02dd/vmlinux-6613476e.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/33195f72f823/Image-6613476e.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5c1ebfe49c5e8e998e75@...kaller.appspotmail.com
>
>   s11: ff60000011241a00 t3 : 0000000000000004 t4 : 1fec00000224849b
>   t5 : 0000000000000002 t6 : 1fec0000022484c6
> status: 0000000200000100 badaddr: ff2000000493ffc0 cause: 000000000000000f
> Kernel panic - not syncing: Kernel stack overflow
> CPU: 1 PID: 3859 Comm: kworker/1:3 Not tainted 6.8.0-rc1-syzkaller #0
> Hardware name: riscv-virtio,qemu (DT)
> Workqueue: usb_hub_wq hub_event
> Call Trace:
> [<ffffffff80010868>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:121
> [<ffffffff858a9b60>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:127
> [<ffffffff85904e9c>] __dump_stack lib/dump_stack.c:88 [inline]
> [<ffffffff85904e9c>] dump_stack_lvl+0xe8/0x154 lib/dump_stack.c:106
> [<ffffffff85904f24>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
> [<ffffffff858aa5b2>] panic+0x33c/0x77a kernel/panic.c:344
> [<ffffffff80010396>] handle_bad_stack+0xe0/0xf4 arch/riscv/kernel/traps.c:412
> [<ffffffff80214a26>] mark_usage kernel/locking/lockdep.c:4599 [inline]
> [<ffffffff80214a26>] __lock_acquire+0xaa8/0x784c kernel/locking/lockdep.c:5091
> SMP: stopping secondary CPUs
> Rebooting in 86400 seconds..
>
>
> ---
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before testing.
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

I ran the reproducer locally all week-end but not luck, it did not 
trigger any panic.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives