WARNING in trace_hardirqs_off_caller

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 359c92c0 Merge tag 'dax-fixes-5.6-rc1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1409496ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=735296e4dd620b10
dashboard link: https://syzkaller.appspot.com/bug?extid=6f4cb1ad9adf9de6f986
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [linux-...@vger.kernel.org mi...@redhat.com ros...@goodmis.org]

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(!irqs_disabled())
WARNING: CPU: 1 PID: 9970 at kernel/locking/lockdep.c:3452 lockdep_hardirqs_off+0x255/0x2e0 kernel/locking/lockdep.c:3452
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 9970 Comm: syz-executor.1 Not tainted 5.6.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x197/0x210 lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:221
__warn.cold+0x2f/0x3e kernel/panic.c:582
report_bug+0x289/0x300 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:267
do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:lockdep_hardirqs_off+0x255/0x2e0 kernel/locking/lockdep.c:3452
Code: 08 84 d2 0f 85 8f 00 00 00 8b 15 46 74 4a 09 85 d2 0f 85 77 ff ff ff 48 c7 c6 60 6b 4b 88 48 c7 c7 a0 6a 4b 88 e8 4a 79 ea ff <0f> 0b e9 5d ff ff ff 48 c7 c7 d4 d3 a5 8a e8 88 d2 58 00 e9 d6 fd
RSP: 0018:ffffc900063bfe98 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8880626a42c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815eab16 RDI: fffff52000c77fc5
RBP: ffffc900063bfeb0 R08: ffff8880626a42c0 R09: fffffbfff137425d
R10: fffffbfff137425c R11: ffffffff89ba12e3 R12: ffffffff81006a3f
R13: ffff8880626a42c0 R14: ffffffff81006a3f R15: 0000000000000000
trace_hardirqs_off_caller+0x65/0x230 kernel/trace/trace_preemptirq.c:73
trace_hardirqs_off_thunk+0x1a/0x1c arch/x86/entry/thunk_64.S:42
entry_SYSCALL_64_after_hwframe+0x3e/0xbe
RIP: 0033:0x45e1fa
Code: 25 18 00 00 00 00 74 01 f0 48 0f b1 3d 4f a7 81 00 48 39 c2 75 da f3 c3 0f 1f 84 00 00 00 00 00 48 63 ff b8 e4 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 06 f3 c3 0f 1f 40 00 48 c7 c2 d4 ff ff ff f7
RSP: 002b:00007ffd0aec8418 EFLAGS: 00000246 ORIG_RAX: 00000000000000e4
RAX: ffffffffffffffda RBX: 00000000000d77fc RCX: 000000000045e1fa
RDX: 0000000000000000 RSI: 00007ffd0aec8420 RDI: 0000000000000001
RBP: 0000000000000df7 R08: 0000000000000001 R09: 0000000002621940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000031
R13: 00007ffd0aec8480 R14: 00000000000d747d R15: 00007ffd0aec8490
Kernel Offset: disabled
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.