[moderation] WARNING: stack recursion on stack type NUM (2)

9 views
Skip to first unread message

syzbot

unread,
Jul 17, 2023, 6:23:49 AM7/17/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: eb26cbb1a754 Merge tag 'platform-drivers-x86-v6.5-2' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1484d574a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=627b9f4ac8bf8945
dashboard link: https://syzkaller.appspot.com/bug?extid=f73e4eb036ace139802f
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-eb26cbb1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6c827255d377/vmlinux-eb26cbb1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4567c584d4d2/bzImage-eb26cbb1.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f73e4e...@syzkaller.appspotmail.com

WARNING: stack recursion on stack type 1
WARNING: can't access registers at entry_SYSCALL_64_after_hwframe+0x63/0xcd


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Oct 11, 2023, 6:18:40 AM10/11/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages