linux-4.9.y boot error: WARNING in cpumask_check

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: e93d4749 Linux 4.9.168
git tree: linux-4.9.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10bc945b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=714671adb236d91c
dashboard link: https://syzkaller.appspot.com/bug?extid=d8c345cff7c2e4b7c470
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

Switched APIC routing to physical x2apic.
..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
smpboot: CPU0: Intel(R) Xeon(R) CPU @ 2.30GHz (family: 0x6, model: 0x3f,
stepping: 0x0)
Performance Events: unsupported p6 CPU model 63 no PMU driver, software
events only.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at ./include/linux/cpumask.h:121
cpumask_check.part.0+0x1c/0x20 include/linux/cpumask.h:121
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.168 #1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
ffff88012b077860 ffffffff82b5f81e ffffffff87c20cc0 fffffbfff0d98bf8
0000000000000000 ffffffff85c8f100 00000000ffffffff 0000000000000000
0000000000000009 ffff88012b077920 ffffffff81671704 0000000041b58ab3
Call Trace:
[<ffffffff82b5f81e>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff82b5f81e>] dump_stack+0x138/0x19a lib/dump_stack.c:51
[<ffffffff81671704>] panic+0x1f2/0x433 kernel/panic.c:180
[<ffffffff816719a2>] __warn.cold+0x2f/0x2f kernel/panic.c:546
[<ffffffff8137350d>] warn_slowpath_null+0x2d/0x40 kernel/panic.c:589
[<ffffffff813f7d3c>] cpumask_check.part.0+0x1c/0x20
include/linux/cpumask.h:121
[<ffffffff81407ee1>] cpumask_check include/linux/cpumask.h:121 [inline]
[<ffffffff81407ee1>] cpumask_test_cpu include/linux/cpumask.h:317 [inline]
[<ffffffff81407ee1>] select_task_rq kernel/sched/core.c:1618 [inline]
[<ffffffff81407ee1>] try_to_wake_up+0x9d1/0xd40 kernel/sched/core.c:2089
[<ffffffff81408260>] wake_up_process+0x10/0x20 kernel/sched/core.c:2166
[<ffffffff813c48a3>] create_worker+0x3a3/0x530 kernel/workqueue.c:1795
[<ffffffff813c9c38>] get_unbound_pool kernel/workqueue.c:3362 [inline]
[<ffffffff813c9c38>] alloc_unbound_pwq+0x748/0xbc0 kernel/workqueue.c:3509
[<ffffffff813d1ae9>] apply_wqattrs_prepare+0x499/0x970
kernel/workqueue.c:3658
[<ffffffff813d2067>] apply_workqueue_attrs_locked+0xa7/0x140
kernel/workqueue.c:3735
[<ffffffff813d2de1>] apply_workqueue_attrs+0x31/0x50
kernel/workqueue.c:3768
[<ffffffff813d5af4>] alloc_and_link_pwqs kernel/workqueue.c:3890 [inline]
[<ffffffff813d5af4>] __alloc_workqueue_key+0x564/0xe80
kernel/workqueue.c:3965
[<ffffffff877c615d>] init_workqueues+0x9b0/0xb47 kernel/workqueue.c:5573
[<ffffffff81002282>] do_one_initcall+0xa2/0x220 init/main.c:780
[<ffffffff8776ec07>] do_pre_smp_initcalls init/main.c:880 [inline]
[<ffffffff8776ec07>] kernel_init_freeable+0x2f1/0x538 init/main.c:1010
[<ffffffff85b71db4>] kernel_init+0x12/0x15e init/main.c:946
[<ffffffff85b8c710>] ret_from_fork+0x40/0x50 arch/x86/entry/entry_64.S:373
Rebooting in 86400 seconds..


---
This bug 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 syzk...@googlegroups.com.

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.