public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bbe6b99feefc3a0842de@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] WARNING in do_notify_parent
Date: Mon, 02 Mar 2026 22:21:27 -0800	[thread overview]
Message-ID: <69a67de7.a70a0220.b118c.000b.GAE@google.com> (raw)
In-Reply-To: <69a313aa.050a0220.3a55be.0042.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    d517cb8cea01 Add linux-next specific files for 20260302
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14051006580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=18bb611e9b1de188
dashboard link: https://syzkaller.appspot.com/bug?extid=bbe6b99feefc3a0842de
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1214b0ba580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10e16202580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3fd9d51aa9e4/disk-d517cb8c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fcada8d480c1/vmlinux-d517cb8c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a4509a43a01d/bzImage-d517cb8c.xz

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

------------[ cut here ]------------
!valid_signal(sig)
WARNING: kernel/signal.c:2174 at do_notify_parent+0xc7e/0xd70 kernel/signal.c:2174, CPU#0: syz.0.17/6060
Modules linked in:
CPU: 0 UID: 0 PID: 6060 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:do_notify_parent+0xc7e/0xd70 kernel/signal.c:2174
Code: c6 05 2c 05 93 0e 01 48 c7 c7 c0 46 cb 8b be a3 08 00 00 48 c7 c2 40 48 cb 8b e8 6d 53 17 00 e9 c6 fa ff ff e8 a3 00 3b 00 90 <0f> 0b 90 45 31 e4 e9 1c ff ff ff e8 92 00 3b 00 90 0f 0b 90 e9 75
RSP: 0018:ffffc90003467c40 EFLAGS: 00010093
RAX: ffffffff818aed2d RBX: dffffc0000000000 RCX: ffff888030320000
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000000000040
RBP: ffffc90003467d90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200068cfa4 R12: ffff888026cf9d10
R13: ffff888030320000 R14: 0000000000000080 R15: 1ffff9200068cf90
FS:  0000000000000000(0000) GS:ffff888124ff7000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4ff1052770 CR3: 0000000077786000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 exit_notify kernel/exit.c:756 [inline]
 do_exit+0x15b3/0x2580 kernel/exit.c:986
 __do_sys_exit kernel/exit.c:1083 [inline]
 __se_sys_exit kernel/exit.c:1081 [inline]
 __x64_sys_exit+0x40/0x40 kernel/exit.c:1081
 x64_sys_call+0x2231/0x2240 arch/x86/include/generated/asm/syscalls_64.h:61
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4ff119c799
Code: Unable to access opcode bytes at 0x7f4ff119c76f.
RSP: 002b:0000200000000d98 EFLAGS: 00000246 ORIG_RAX: 000000000000003c
RAX: ffffffffffffffda RBX: 000000000000000b RCX: 00007f4ff119c799
RDX: 00007f4ff119c799 RSI: 0000200000000dc0 RDI: 000000000000000b
RBP: 00007f4ff1232bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4ff1415fac R14: 00007f4ff1415fa0 R15: 00007f4ff1415fa0
 </TASK>


---
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.

  reply	other threads:[~2026-03-03  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 16:11 [syzbot] [kernel?] WARNING in do_notify_parent syzbot
2026-03-03  6:21 ` syzbot [this message]
2026-03-07  5:28 ` Forwarded: [PATCH] kernel/fork: validate exit_signal in clone() syscall syzbot
2026-03-16  8:21 ` Forwarded: [PATCH] kernel/fork: validate exit_signal in kernel_clone() syzbot
     [not found] <20260307052823.351759-1-kartikey406@gmail.com>
2026-03-07  5:53 ` [syzbot] [kernel?] WARNING in do_notify_parent syzbot
     [not found] <20260316082100.554362-1-kartikey406@gmail.com>
2026-03-16  9:23 ` syzbot

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=69a67de7.a70a0220.b118c.000b.GAE@google.com \
    --to=syzbot+bbe6b99feefc3a0842de@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