linux-kernel - [syzbot] [kernel?] WARNING in sched_mm_cid_remote

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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67429e81.050a0220.1cc393.002d.GAE@google.com>
Date: Sat, 23 Nov 2024 19:33:21 -0800
From: syzbot <syzbot+0784d42fd852319c56a4@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, luto@...nel.org, peterz@...radead.org, 
	syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: [syzbot] [kernel?] WARNING in sched_mm_cid_remote_clear (2)

Hello,

syzbot found the following issue on:

HEAD commit:    a5c93bfec0be Merge tag 'x86-mm-2024-11-18' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16d986c0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=881d13977c7330ad
dashboard link: https://syzkaller.appspot.com/bug?extid=0784d42fd852319c56a4
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: https://storage.googleapis.com/syzbot-assets/5a79011a6168/disk-a5c93bfe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/35d2b8ddacb6/vmlinux-a5c93bfe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/521d7aa8240a/bzImage-a5c93bfe.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6707 at include/linux/cpumask.h:135 cpu_max_bits_warn include/linux/cpumask.h:135 [inline]
WARNING: CPU: 0 PID: 6707 at include/linux/cpumask.h:135 cpumask_check include/linux/cpumask.h:142 [inline]
WARNING: CPU: 0 PID: 6707 at include/linux/cpumask.h:135 cpumask_clear_cpu include/linux/cpumask.h:536 [inline]
WARNING: CPU: 0 PID: 6707 at include/linux/cpumask.h:135 __mm_cid_put kernel/sched/sched.h:3599 [inline]
WARNING: CPU: 0 PID: 6707 at include/linux/cpumask.h:135 sched_mm_cid_remote_clear+0x48a/0x4f0 kernel/sched/core.c:10474
Modules linked in:
CPU: 0 UID: 0 PID: 6707 Comm: syz-executor Not tainted 6.12.0-syzkaller-01518-ga5c93bfec0be #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:cpu_max_bits_warn include/linux/cpumask.h:135 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:142 [inline]
RIP: 0010:cpumask_clear_cpu include/linux/cpumask.h:536 [inline]
RIP: 0010:__mm_cid_put kernel/sched/sched.h:3599 [inline]
RIP: 0010:sched_mm_cid_remote_clear+0x48a/0x4f0 kernel/sched/core.c:10474
Code: 0e 01 e8 19 6a 0d 00 eb 9d 4c 89 ef e8 ff ed 91 00 e9 66 fc ff ff e8 f5 ed 91 00 e9 46 fd ff ff 89 44 24 48 e9 16 fe ff ff 90 <0f> 0b 90 e9 ef fd ff ff e8 f9 b3 c7 09 e9 06 ff ff ff 48 89 d6 48
RSP: 0018:ffffc9001c567cf8 EFLAGS: 00010006
RAX: 000000000000001f RBX: ffffe8ffffd37180 RCX: ffffffff815ca5c2
RDX: 00000000ffffffff RSI: 0000000000000004 RDI: ffffc9001c567d40
RBP: 1ffff920038acfa0 R08: 0000000000000001 R09: fffff520038acfa8
R10: 0000000000000003 R11: 0000000000000000 R12: ffff888028574390
R13: ffffe8ffffd37188 R14: 0000000000000200 R15: ffff8880b873eec0
FS:  00005555936c8500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30d14ff8 CR3: 000000002fe54000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 sched_mm_cid_remote_clear_old kernel/sched/core.c:10507 [inline]
 task_mm_cid_work+0x39e/0x930 kernel/sched/core.c:10557
 task_work_run+0x151/0x250 kernel/task_work.c:239
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
 irqentry_exit_to_user_mode+0x25c/0x280 kernel/entry/common.c:231
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7fc4b4f51dc0
Code: 66 2e 0f 1f 84 00 00 00 00 00 48 8d 47 0d c3 66 66 2e 0f 1f 84 00 00 00 00 00 48 8d 47 0e c3 66 2e 0f 1f 84 00 00 00 00 00 90 <c5> f9 6e c6 89 f8 25 ff 0f 00 00 c4 e2 7d 78 c0 c5 f1 ef c9 3d e0
RSP: 002b:00007ffedb2eba78 EFLAGS: 00010246
RAX: 00007ffedb2ec180 RBX: 00007ffedb2ebfe0 RCX: 0000000000000000
RDX: 00007ffedb2ec160 RSI: 0000000000000025 RDI: 00007fc4b4ff2d5a
RBP: 00000000fbad8001 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc4b4ff2d5a
R13: 00007ffedb2ec160 R14: 0000000000000000 R15: 00007ffedb2ebfe0
 </TASK>


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