From: syzbot <syzbot+9ca2c6e6b098bf5ae60a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wangjinchao600@gmail.com
Subject: Re: [syzbot] [fs?] [mm?] WARNING in sched_mm_cid_fork
Date: Tue, 23 Dec 2025 19:50:03 -0800 [thread overview]
Message-ID: <694b62eb.050a0220.35954c.0011.GAE@google.com> (raw)
In-Reply-To: <aUtfNFhP9d3k6Ray@ndev>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in sched_mm_cid_fork
------------[ cut here ]------------
WARNING: kernel/sched/core.c:10569 at sched_mm_cid_fork+0x66/0xc30 kernel/sched/core.c:10569, CPU#0: kworker/u4:21/5944
Modules linked in:
CPU: 0 UID: 0 PID: 5944 Comm: kworker/u4:21 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:sched_mm_cid_fork+0x66/0xc30 kernel/sched/core.c:10569
Code: 4c 8b 3b 4d 85 ff 74 21 49 8d 9d d4 15 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 30 84 c0 0f 85 13 0a 00 00 31 c0 3b 03 70 04 90 <0f> 0b 90 49 8d 9f 00 01 00 00 49 8d bf c0 01 00 00 48 89 7c 24 20
RSP: 0018:ffffc900037d7c18 EFLAGS: 00010246
RAX: 1ffff110069940b3 RBX: ffff888034ca0598 RCX: ffff888034ca0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888034ca0000
RBP: ffffc900037d7da8 R08: ffffffff8e095e83 R09: 1ffffffff1c12bd0
R10: dffffc0000000000 R11: fffffbfff1c12bd1 R12: ffff888034ca0000
R13: ffff888034ca0000 R14: dffffc0000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff88808d416000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6acae1a000 CR3: 0000000040cc0000 CR4: 0000000000352ef0
Call Trace:
<TASK>
bprm_execve+0xd88/0x1400 fs/exec.c:1776
kernel_execve+0x8f0/0x9f0 fs/exec.c:1919
call_usermodehelper_exec_async+0x210/0x360 kernel/umh.c:109
ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
</TASK>
Tested on:
commit: b9275466 Merge tag 'dma-mapping-6.19-2025-12-22' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12be2022580000
kernel config: https://syzkaller.appspot.com/x/.config?x=513255d80ab78f2b
dashboard link: https://syzkaller.appspot.com/bug?extid=9ca2c6e6b098bf5ae60a
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
next parent reply other threads:[~2025-12-24 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aUtfNFhP9d3k6Ray@ndev>
2025-12-24 3:50 ` syzbot [this message]
[not found] <20251223103927.2414466-2-wangjinchao600@gmail.com>
2025-12-23 10:55 ` [syzbot] [fs?] [mm?] WARNING in sched_mm_cid_fork syzbot
2025-12-18 2:24 [PATCH] exec: do not call sched_mm_cid_after_execve() on exec fail Jinchao Wang
2025-12-18 2:46 ` [syzbot] [fs?] [mm?] WARNING in sched_mm_cid_fork syzbot
[not found] <20251218014920.41867-2-wangjinchao600@gmail.com>
2025-12-18 2:12 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-12-03 5:15 syzbot
2025-12-12 0:25 ` 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=694b62eb.050a0220.35954c.0011.GAE@google.com \
--to=syzbot+9ca2c6e6b098bf5ae60a@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wangjinchao600@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.