general protection fault in lockdep_invariant_state

[syzbot]

Hello,

syzkaller hit the following crash on
744c56def80933f393da5790862f21acdcfc816d
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.


CC: [h...@zytor.com jko...@suse.cz jpoi...@redhat.com
linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com
tg...@linutronix.de thga...@google.com x...@kernel.org]

RBP: 0000000000000450 R08: 00000000208d0000 R09: 0000000000000000
R10: 0000000020dfdffc R11: 0000000000000216 R12: 00000000004b721f
R13: 0000000000000005 R14: 0000000000000000 R15: 0000000020000000
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 0 PID: 6116 Comm: syz-executor6 Not tainted 4.13.0-next-20170905+ #15
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8801cd3f2240 task.stack: ffff8801cd3f8000
RIP: 0010:invalidate_xhlock kernel/locking/lockdep.c:4717 [inline]
RIP: 0010:lockdep_invariant_state+0xd6/0x120 kernel/locking/lockdep.c:4791
RSP: 0018:ffff8801cd3ffe38 EFLAGS: 00010002
RAX: dffffc0000000000 RBX: 0000000000001d88 RCX: 0000000000000000
RDX: 00000000000003bc RSI: 0000000000000000 RDI: 0000000000001de0
RBP: ffff8801cd3ffe48 R08: ffff88021fffae78 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffff8801cd3ffee0 R14: ffff8801cd3f2240 R15: ffffffff85ac9830
FS: 00007ff58001c700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff58001ca08 CR3: 00000001ca724000 CR4: 00000000001406f0
DR0: 0000000020001010 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
lockdep_sys_exit+0x47/0xf0 kernel/locking/lockdep.c:4627
prepare_exit_to_usermode arch/x86/entry/common.c:192 [inline]
syscall_return_slowpath+0x244/0x500 arch/x86/entry/common.c:266
ret_from_fork+0x15/0x40 arch/x86/entry/entry_64.S:423
RIP: 0033:0x451e59
RSP: 002b:0000000020000000 EFLAGS: 00000216 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 00000000007180b0 RCX: 0000000000451e59
RDX: 0000000020001000 RSI: 0000000020000000 RDI: 0000000000000000
RBP: 0000000000000450 R08: 00000000208d0000 R09: 0000000000000000
R10: 0000000020dfdffc R11: 0000000000000216 R12: 00000000004b721f
R13: 0000000000000005 R14: 0000000000000000 R15: 0000000020000000
Code: 83 a0 11 00 00 83 e0 3f 48 89 c2 48 c1 e2 04 48 29 c2 48 b8 00 00 00
00 00 fc ff df 49 8d 1c d4 48 8d 7b 58 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 2f 48 c7 43 58 00 00 00 00 5b 41 5c 5d c3 0f ff
RIP: invalidate_xhlock kernel/locking/lockdep.c:4717 [inline] RSP:
ffff8801cd3ffe38
RIP: lockdep_invariant_state+0xd6/0x120 kernel/locking/lockdep.c:4791 RSP:
ffff8801cd3ffe38
---[ end trace 2d91155d0b1cd6b3 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

Seems to stop happening on Oct 12, no reproducer, I am going to close
this, let's see if it happens again:

#syz invalid

On Mon, Oct 30, 2017 at 10:36 PM, syzbot
<bot+1abf0632466543363d...@syzkaller.appspotmail.com>
wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a1140ad880e33c3055cc8c0b6%40google.com.
> For more options, visit https://groups.google.com/d/optout.