Hello, syzbot found the following issue on: HEAD commit: a9c9a6f741cd Merge tag 'scsi-misc' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=101320a5300000 kernel config: https://syzkaller.appspot.com/x/.config?x=7860a0536ececf0c dashboard link: https://syzkaller.appspot.com/bug?extid=3361d05142f53b068ca1 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=121ce115300000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110adea3300000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+3361d05142f53b068ca1@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 8408 at mm/util.c:597 kvmalloc_node+0x111/0x120 mm/util.c:597 Modules linked in: CPU: 0 PID: 8408 Comm: syz-executor725 Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:kvmalloc_node+0x111/0x120 mm/util.c:597 Code: 01 00 00 00 4c 89 e7 e8 8d 12 0d 00 49 89 c5 e9 69 ff ff ff e8 f0 21 d1 ff 41 89 ed 41 81 cd 00 20 01 00 eb 95 e8 df 21 d1 ff <0f> 0b e9 4c ff ff ff 0f 1f 84 00 00 00 00 00 55 48 89 fd 53 e8 c6 RSP: 0018:ffffc9000c6df720 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffffc9000c6dfe18 RCX: 0000000000000000 RDX: ffff88801ff68000 RSI: ffffffff81a4f621 RDI: 0000000000000003 RBP: 0000000000002dc0 R08: 000000007fffffff R09: 00000000ffffffff R10: ffffffff81a4f5de R11: 0000000000000000 R12: 000000020008a100 R13: 0000000000000000 R14: 00000000ffffffff R15: ffff888014594000 FS: 0000000000ba0300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f63094ed6c0 CR3: 000000001ddbe000 CR4: 0000000000350ef0 Call Trace: kvmalloc include/linux/mm.h:806 [inline] kvmalloc_array include/linux/mm.h:824 [inline] kvcalloc include/linux/mm.h:829 [inline] check_btf_line+0x1a9/0xad0 kernel/bpf/verifier.c:9925 check_btf_info kernel/bpf/verifier.c:10049 [inline] bpf_check+0x1636/0xbd20 kernel/bpf/verifier.c:13759 bpf_prog_load+0xe57/0x21f0 kernel/bpf/syscall.c:2301 __sys_bpf+0x67e/0x5df0 kernel/bpf/syscall.c:4587 __do_sys_bpf kernel/bpf/syscall.c:4691 [inline] __se_sys_bpf kernel/bpf/syscall.c:4689 [inline] __x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:4689 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x43f0a9 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc34347988 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 RAX: ffffffffffffffda RBX: 0000000000400488 RCX: 000000000043f0a9 RDX: 0000000000000078 RSI: 0000000020008a40 RDI: 0000000000000005 RBP: 0000000000403090 R08: 00000000004ac018 R09: 0000000000400488 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000403120 R13: 0000000000000000 R14: 00000000004ac018 R15: 0000000000400488 --- 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@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
