kernel BUG at arch/x86/mm/physaddr.c:LINE! (3)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: dce0f886 Linux 4.19.132
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=144041eb100000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea24367973479f36
dashboard link: https://syzkaller.appspot.com/bug?extid=d229bfbdb33b5139e86f
compiler: gcc (GCC) 10.1.0-syz 20200507

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

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:27!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3698 Comm: systemd-udevd Not tainted 4.19.132-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__phys_addr+0xa7/0x110 arch/x86/mm/physaddr.c:27
Code: d9 7c 08 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 70 bd 38 00 48 85 db 75 0d e8 d6 bb 38 00 4c 89 e0 5b 5d 41 5c c3 e8 c9 bb 38 00 <0f> 0b e8 c2 bb 38 00 48 c7 c0 10 50 c7 88 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff88808ef9fb30 EFLAGS: 00010293
RAX: ffff88808ef90400 RBX: 0007700007777770 RCX: ffffffff8130ec18
RDX: 0000000000000000 RSI: ffffffff8130ec77 RDI: 0000000000000006
RBP: 0007700087777770 R08: 0000000000000000 R09: 0007700087777770
R10: 0000000000000006 R11: 0000000000000000 R12: 0007e78007777770
R13: ffff88808ef9fb88 R14: 0000000000000000 R15: 0000000000000286
FS: 00007f03d7eb28c0(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005622ba5154b8 CR3: 000000008e8c0000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
virt_to_head_page include/linux/mm.h:665 [inline]
qlink_to_cache mm/kasan/quarantine.c:127 [inline]
qlist_free_all+0xbb/0x140 mm/kasan/quarantine.c:163
quarantine_reduce+0x1a9/0x230 mm/kasan/quarantine.c:259
kasan_kmalloc+0xa2/0x160 mm/kasan/kasan.c:538
slab_post_alloc_hook mm/slab.h:445 [inline]
slab_alloc mm/slab.c:3397 [inline]
kmem_cache_alloc+0x110/0x370 mm/slab.c:3557
prepare_creds+0x39/0x510 kernel/cred.c:255
do_faccessat+0x94/0x7a0 fs/open.c:359
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f03d6d259c7
Code: 83 c4 08 48 3d 01 f0 ff ff 73 01 c3 48 8b 0d c8 d4 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 15 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 d4 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007ffe1dcff2d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00005622ba4e1c00 RCX: 00007f03d6d259c7
RDX: 00746e657665752f RSI: 0000000000000000 RDI: 00007ffe1dcff2e0
RBP: 00007ffe1dcff350 R08: 0000000000000c21 R09: 0000000000001010
R10: 00007f03d6fe3b58 R11: 0000000000000246 R12: 00005622b8632856
R13: 00005622ba4de570 R14: 00007ffe1dcff2e0 R15: 00007ffe1dcff420
Modules linked in:
---[ end trace 6240b6a4886a3a5c ]---
RIP: 0010:__phys_addr+0xa7/0x110 arch/x86/mm/physaddr.c:27
Code: d9 7c 08 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 70 bd 38 00 48 85 db 75 0d e8 d6 bb 38 00 4c 89 e0 5b 5d 41 5c c3 e8 c9 bb 38 00 <0f> 0b e8 c2 bb 38 00 48 c7 c0 10 50 c7 88 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff88808ef9fb30 EFLAGS: 00010293
RAX: ffff88808ef90400 RBX: 0007700007777770 RCX: ffffffff8130ec18
RDX: 0000000000000000 RSI: ffffffff8130ec77 RDI: 0000000000000006
RBP: 0007700087777770 R08: 0000000000000000 R09: 0007700087777770
R10: 0000000000000006 R11: 0000000000000000 R12: 0007e78007777770
R13: ffff88808ef9fb88 R14: 0000000000000000 R15: 0000000000000286
FS: 00007f03d7eb28c0(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005622ba5154b8 CR3: 000000008e8c0000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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