BUG: spinlock bad magic in batadv_tt_purge

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1495f8f7b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=f7c9eba1e68c4a49f7b9
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

BUG: spinlock bad magic on CPU#1, kworker/u4:1/12396
lock: 0xffff88800012c7f8, .magic: 00000000, .owner: <none>/-1, .owner_cpu: -1
CPU: 1 PID: 12396 Comm: kworker/u4:1 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_tt_purge
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
do_raw_spin_lock+0x19f/0x220 kernel/locking/spinlock_debug.c:112
spin_lock_bh include/linux/spinlock.h:334 [inline]
batadv_tt_global_purge net/batman-adv/translation-table.c:2521 [inline]
batadv_tt_purge+0x123/0xa00 net/batman-adv/translation-table.c:3812
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
audit: type=1800 audit(1642049700.464:736): pid=20253 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="bus" dev="sda1" ino=14165 res=0
audit: type=1800 audit(1642049700.964:737): pid=20300 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="bus" dev="sda1" ino=14784 res=0
audit: type=1800 audit(1642049701.914:738): pid=20456 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="bus" dev="sda1" ino=14165 res=0
------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:27!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 20710 Comm: systemd-udevd Not tainted 4.19.211-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: 67 fb 09 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 40 28 37 00 48 85 db 75 0d e8 a6 26 37 00 4c 89 e0 5b 5d 41 5c c3 e8 99 26 37 00 <0f> 0b e8 92 26 37 00 48 c7 c0 10 30 e7 89 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff888040b2faf8 EFLAGS: 00010293
RAX: ffff88801e156240 RBX: 0000077007700077 RCX: ffffffff812b5e78
RDX: 0000000000000000 RSI: ffffffff812b5ed7 RDI: 0000000000000006
RBP: 0000077087700077 R08: 0000000000000000 R09: 0000077087700077
R10: 0000000000000006 R11: 0000000000000009 R12: 00007ef007700077
R13: ffff888040b2fb50 R14: 0000000000000000 R15: 0000000000000286
FS: 00007fb353f208c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd559c0957 CR3: 00000000251e2000 CR4: 00000000003426f0
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
getname_flags+0xce/0x590 fs/namei.c:140
do_sys_open+0x26c/0x520 fs/open.c:1079
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fb353066840
Code: 73 01 c3 48 8b 0d 68 77 20 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 89 bb 20 00 00 75 10 b8 02 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 1e f6 ff ff 48 89 04 24
RSP: 002b:00007ffd559c2ae8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000563ccc9ad520 RCX: 00007fb353066840
RDX: 0000563ccc36bfe3 RSI: 00000000000a0800 RDI: 0000563ccc9bf7c0
RBP: 00007ffd559c2c60 R08: 0000563ccc36b670 R09: 0000000000000010
R10: 0000563ccc36bd0c R11: 0000000000000246 R12: 00007ffd559c2bb0
R13: 0000563ccc9beab0 R14: 0000000000000003 R15: 000000000000000e
Modules linked in:
---[ end trace b5630a1edfbaad0c ]---
RIP: 0010:__phys_addr+0xa7/0x110 arch/x86/mm/physaddr.c:27
Code: 67 fb 09 4c 89 e3 31 ff 48 d3 eb 48 89 de e8 40 28 37 00 48 85 db 75 0d e8 a6 26 37 00 4c 89 e0 5b 5d 41 5c c3 e8 99 26 37 00 <0f> 0b e8 92 26 37 00 48 c7 c0 10 30 e7 89 48 ba 00 00 00 00 00 fc
RSP: 0018:ffff888040b2faf8 EFLAGS: 00010293
RAX: ffff88801e156240 RBX: 0000077007700077 RCX: ffffffff812b5e78
RDX: 0000000000000000 RSI: ffffffff812b5ed7 RDI: 0000000000000006
RBP: 0000077087700077 R08: 0000000000000000 R09: 0000077087700077
R10: 0000000000000006 R11: 0000000000000009 R12: 00007ef007700077
R13: ffff888040b2fb50 R14: 0000000000000000 R15: 0000000000000286
FS: 00007fb353f208c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd559c0957 CR3: 00000000251e2000 CR4: 00000000003426f0
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.