MIME-Version: 1.0
Date:   Thu, 09 Mar 2023 16:42:47 -0800
Message-ID: <0000000000004d318a05f6810a9f@google.com>
Subject: [syzbot] [kernel?] WARNING in c_start (2)
From:   syzbot <syzbot+96cae094d90877641f32@syzkaller.appspotmail.com>
To:     bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
        linux-kernel@vger.kernel.org, mingo@redhat.com,
        syzkaller-bugs@googlegroups.com, tglx@linutronix.de, x86@kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hello,

syzbot found the following issue on:

HEAD commit:    44889ba56cbb Merge tag 'net-6.3-rc2' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13933824c80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d677dcd743eef09
dashboard link: https://syzkaller.appspot.com/bug?extid=96cae094d90877641f32
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

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

------------[ cut here ]------------
WARNING: CPU: 3 PID: 5136 at include/linux/cpumask.h:143 cpu_max_bits_warn include/linux/cpumask.h:143 [inline]
WARNING: CPU: 3 PID: 5136 at include/linux/cpumask.h:143 cpumask_check include/linux/cpumask.h:150 [inline]
WARNING: CPU: 3 PID: 5136 at include/linux/cpumask.h:143 cpumask_next include/linux/cpumask.h:212 [inline]
WARNING: CPU: 3 PID: 5136 at include/linux/cpumask.h:143 c_start+0x1da/0x250 arch/x86/kernel/cpu/proc.c:156
Modules linked in:
CPU: 3 PID: 5136 Comm: syz-fuzzer Not tainted 6.3.0-rc1-syzkaller-00106-g44889ba56cbb #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:cpu_max_bits_warn include/linux/cpumask.h:143 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:150 [inline]
RIP: 0010:cpumask_next include/linux/cpumask.h:212 [inline]
RIP: 0010:c_start+0x1da/0x250 arch/x86/kernel/cpu/proc.c:156
Code: 49 11 8c e8 88 a9 51 00 4c 89 e0 5b 5d 41 5c 41 5d 41 5e c3 f3 48 0f bc db e8 72 a9 51 00 89 db e9 38 ff ff ff e8 66 a9 51 00 <0f> 0b e9 c1 fe ff ff 48 c7 c7 80 7f 77 8e e8 d3 49 a2 00 e9 67 ff
RSP: 0018:ffffc90001ee7c68 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000007 RCX: 0000000000000000
RDX: ffff888023996000 RSI: ffffffff813279da RDI: 0000000000000004
RBP: ffffffff8e777f80 R08: 0000000000000004 R09: 0000000000000007
R10: 0000000000000004 R11: 0000000000000000 R12: ffff88801f2ded60
R13: 0000000000000008 R14: 0000000000000004 R15: 0000000000000000
FS:  0000000001ec53d0(0000) GS:ffff88802cb80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f08961ed698 CR3: 00000000141a7000 CR4: 0000000000150ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 seq_read_iter+0x2ca/0x12d0 fs/seq_file.c:225
 proc_reg_read_iter+0x115/0x2d0 fs/proc/inode.c:301
 call_read_iter include/linux/fs.h:1845 [inline]
 new_sync_read fs/read_write.c:389 [inline]
 vfs_read+0x681/0x930 fs/read_write.c:470
 ksys_read+0x12b/0x250 fs/read_write.c:613
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x403ace
Code: 48 89 6c 24 38 48 8d 6c 24 38 e8 0d 00 00 00 48 8b 6c 24 38 48 83 c4 40 c3 cc cc cc 49 89 f2 48 89 fa 48 89 ce 48 89 df 0f 05 <48> 3d 01 f0 ff ff 76 15 48 f7 d8 48 89 c1 48 c7 c0 ff ff ff ff 48
RSP: 002b:000000c000561308 EFLAGS: 00000202 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000403ace
RDX: 0000000000000b49 RSI: 000000c0003ae4b7 RDI: 0000000000000003
RBP: 000000c000561348 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000c000561488
R13: 0000000000000000 R14: 000000c0000061a0 R15: 0000000000000001
 </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@googlegroups.com.

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