public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8fdf0d8e10bdde1c2e88@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [kernel?] WARNING in do_exit
Date: Sat, 02 May 2026 05:20:28 -0700	[thread overview]
Message-ID: <69f5ec0c.050a0220.312cd3.0023.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    3b3bea6d4b9c Merge tag 'cgroup-for-7.1-rc1-fixes' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105a7236580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=59da38148f3a3d24
dashboard link: https://syzkaller.appspot.com/bug?extid=8fdf0d8e10bdde1c2e88
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-3b3bea6d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9e011051a02c/vmlinux-3b3bea6d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dd9d977be0e6/bzImage-3b3bea6d.xz

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

WARNING: kernel/signal.c:2174 at do_notify_parent+0xea8/0x10b0 kernel/signal.c:2174, CPU#2: syz.2.2072/13056
Kernel panic - n\0o\0t sync\0i\0n\0g\0:\0 \0k\0e\0r\0n\0e\0l\0:\0 \0panic_on_warn set ...
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 check_panic_on_warn kernel/panic.c:524 [inline]
 check_panic_on_warn.cold+0x19/0x34 kernel/panic.c:519
 __warn.cold+0x191/0x328 kernel/panic.c:1103
 asm_exc_invalid_op+0x1a/0x20 arch/x86/include/asm/idtentry.h:616
RSP: 0018:ffffc9000f407aa8 EFLAGS: 00010093
RDX: ffff88805386ca00 RSI: ffffffff81caad07 RDI: ffff88805386ca00
R10: 0000000000000080 R11: 0000000000000000 R12: 1ffff92001e80f58
 exit_notify kernel/exit.c:757 [inline]
 do_exit+0x1b05/0x2a60 kernel/exit.c:987
 get_signal+0x1ec7/0x21e0 kernel/signal.c:3037
 asm_exc_general_protection+0x26/0x30 arch/x86/include/asm/idtentry.h:612
RSP: 002b:00002000000001e0 EFLAGS: 00010217
R13: 00007fcbfe616038 R14: 00007fcbfe615fa0 R15: 00007ffd58e78548
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 syzkaller@googlegroups.com.

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

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

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

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

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

                 reply	other threads:[~2026-05-02 12:20 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=69f5ec0c.050a0220.312cd3.0023.GAE@google.com \
    --to=syzbot+8fdf0d8e10bdde1c2e88@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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