BUG: unable to handle kernel paging request in __get_vm_area_node

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9a73fa375d58 Merge branch 'for-5.14-fixes' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ab55e9300000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3a20bae04b96ccd
dashboard link: https://syzkaller.appspot.com/bug?extid=8117530c00a397f952c1
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
userspace arch: i386
CC: [linux-...@vger.kernel.org penguin...@I-love.SAKURA.ne.jp ros...@goodmis.org tg...@linutronix.de]

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+811753...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: fffff52006984000
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 23ffee067 P4D 23ffee067 PUD 109ad067 PMD 10c067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 16087 Comm: syz-executor.0 Not tainted 5.14.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:64
Code: c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01
RSP: 0018:ffffc90004187550 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffffc900198e7000 RCX: 0000000000c9d15a
RDX: 000000000430435a RSI: 0000000000000000 RDI: fffff52006984000
RBP: 0000000021821acc R08: 00001ffffffffffe R09: fffff5200331ce00
R10: ffffffff81b0f966 R11: 000000000000003f R12: ffff88802cac0b00
R13: 0000000000000001 R14: 0000000021821acc R15: 00000000ffffffff
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0063) knlGS:00000000f55d8b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffff52006984000 CR3: 0000000062e7f000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
kasan_unpoison mm/kasan/shadow.c:138 [inline]
kasan_unpoison+0x3c/0x60 mm/kasan/shadow.c:115
__get_vm_area_node.constprop.0+0x173/0x380 mm/vmalloc.c:2395
__vmalloc_node_range+0x12e/0x960 mm/vmalloc.c:2956
__vmalloc_node mm/vmalloc.c:3015 [inline]
vzalloc+0x67/0x80 mm/vmalloc.c:3085
profile_init+0xd1/0x110 kernel/profile.c:127
profiling_store+0x5e/0xd0 kernel/ksysfs.c:80
kobj_attr_store+0x50/0x80 lib/kobject.c:856
sysfs_kf_write+0x110/0x160 fs/sysfs/file.c:139
kernfs_fop_write_iter+0x342/0x500 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2114 [inline]
do_iter_readv_writev+0x46f/0x740 fs/read_write.c:740
do_iter_write+0x188/0x670 fs/read_write.c:866
vfs_iter_write+0x70/0xa0 fs/read_write.c:907
iter_file_splice_write+0x723/0xc70 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0x110/0x180 fs/splice.c:936
splice_direct_to_actor+0x34b/0x8c0 fs/splice.c:891
do_splice_direct+0x1b3/0x280 fs/splice.c:979
do_sendfile+0x9f0/0x1120 fs/read_write.c:1260
__do_compat_sys_sendfile fs/read_write.c:1346 [inline]
__se_compat_sys_sendfile fs/read_write.c:1329 [inline]
__ia32_compat_sys_sendfile+0x1dd/0x220 fs/read_write.c:1329
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178
do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:203
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
RIP: 0023:0xf7fde549
Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f55d85fc EFLAGS: 00000296 ORIG_RAX: 00000000000000bb
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000000003
RDX: 0000000000000000 RSI: 00000000000000a7 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: fffff52006984000
---[ end trace 5606a67234717d0b ]---
RIP: 0010:memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:64
Code: c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01
RSP: 0018:ffffc90004187550 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffffc900198e7000 RCX: 0000000000c9d15a
RDX: 000000000430435a RSI: 0000000000000000 RDI: fffff52006984000
RBP: 0000000021821acc R08: 00001ffffffffffe R09: fffff5200331ce00
R10: ffffffff81b0f966 R11: 000000000000003f R12: ffff88802cac0b00
R13: 0000000000000001 R14: 0000000021821acc R15: 00000000ffffffff
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0063) knlGS:00000000f55d8b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffff52006984000 CR3: 0000000062e7f000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

syzbot will keep track of this issue. 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.