general protection fault in lock_is_held_type

[syzbot]

Hello,

syzbot hit the following crash on upstream commit
18b7fd1c93e5204355ddbf2608a097d64df81b88 (Sat Apr 14 15:50:50 2018 +0000)
Merge branch 'akpm' (patches from Andrew)
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=fea25d0a45f1ac9af2b4

Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=4804496370696192
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-8852471259444315113
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [core...@netfilter.org da...@davemloft.net f...@strlen.de
ho...@verge.net.au j...@ssi.bg kad...@blackhole.kfki.hu
linux-...@vger.kernel.org lvs-...@vger.kernel.org
net...@vger.kernel.org netfilt...@vger.kernel.org pa...@netfilter.org
wen...@linux-vs.org]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+fea25d...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

IPVS: ip_vs_svc_hash(): request for already hashed, called from
do_ip_vs_set_ctl+0x1b43/0x1d30 net/netfilter/ipvs/ip_vs_ctl.c:2457
kasan: CONFIG_KASAN_INLINE enabled
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
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: 1 PID: 30603 Comm: syz-executor7 Not tainted 4.16.0+ #3
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:lock_is_held_type+0x35/0x210 kernel/locking/lockdep.c:3951
RSP: 0018:ffff8801db107e50 EFLAGS: 00010803
RAX: dffffc0000000000 RBX: ffff8801c3afc540 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: ffff8801c3afcd74
RBP: ffff8801db107e70 R08: ffffed003b6246c3 R09: ffffed003b6246c2
R10: ffffed003b6246c2 R11: ffff8801db123613 R12: 1ffff1003b620ff0
R13: ffffffff88b8dee0 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f5899cb8700(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f73ef4d3518 CR3: 00000001cf11b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
lock_is_held include/linux/lockdep.h:344 [inline]
rcu_read_lock_sched_held+0x108/0x120 kernel/rcu/update.c:117
trace_local_timer_entry arch/x86/include/asm/trace/irq_vectors.h:56
[inline]
smp_apic_timer_interrupt+0x55e/0x710 arch/x86/kernel/apic/apic.c:1049
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:862
</IRQ>
RIP: 0010:lock_release+0x4ed/0xa10 kernel/locking/lockdep.c:3929
RSP: 0018:ffff88018cade7b0 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff13
RAX: dffffc0000000000 RBX: ffffed003195bcfb RCX: 1ffff1003875f9ad
RDX: 1ffffffff11630ed RSI: 0000000000000002 RDI: 0000000000000282
RBP: ffff88018cade8e0 R08: 1ffff1003195bcff R09: ffffed003b6246c2
R10: 0000000000000003 R11: 0000000000000001 R12: ffff8801c3afc540
R13: ffffffff88b8df60 R14: ffff8801c3afc540 R15: ffff88018cade7f8
rcu_lock_release include/linux/rcupdate.h:251 [inline]
rcu_read_unlock include/linux/rcupdate.h:688 [inline]
__unlock_page_memcg+0x72/0x100 mm/memcontrol.c:1654
unlock_page_memcg+0x2c/0x40 mm/memcontrol.c:1663
page_remove_file_rmap mm/rmap.c:1248 [inline]
page_remove_rmap+0x6f2/0x1250 mm/rmap.c:1299
zap_pte_range mm/memory.c:1337 [inline]
zap_pmd_range mm/memory.c:1441 [inline]
zap_pud_range mm/memory.c:1470 [inline]
zap_p4d_range mm/memory.c:1491 [inline]
unmap_page_range+0xeb4/0x2200 mm/memory.c:1512
unmap_single_vma+0x1a0/0x310 mm/memory.c:1557
unmap_vmas+0x120/0x1f0 mm/memory.c:1587
exit_mmap+0x265/0x570 mm/mmap.c:3038
__mmput kernel/fork.c:962 [inline]
mmput+0x251/0x610 kernel/fork.c:983
exit_mm kernel/exit.c:544 [inline]
do_exit+0xe98/0x2730 kernel/exit.c:852
do_group_exit+0x16f/0x430 kernel/exit.c:968
get_signal+0x886/0x1960 kernel/signal.c:2469
do_signal+0x98/0x2040 arch/x86/kernel/signal.c:810
exit_to_usermode_loop+0x28a/0x310 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:196 [inline]
syscall_return_slowpath arch/x86/entry/common.c:265 [inline]
do_syscall_64+0x792/0x9d0 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x455319
RSP: 002b:00007f5899cb7ce8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000072bf80 RCX: 0000000000455319
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000072bf80
RBP: 000000000072bf80 R08: 0000000000000000 R09: 000000000072bf58
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000a3e81f R14: 00007f5899cb89c0 R15: 0000000000000001
Code: 55 48 89 e5 41 55 49 89 fd 41 54 53 65 48 8b 1c 25 c0 ed 01 00 48 8d
bb 34 08 00 00 48 89 fa 48 83 ec 08 48 c1 ea 03 0f b6 14 02 <48> 03 00 00
00 00 00 00 00 00 30 4d 06 00 c9 ff ff 00 00 00 00
RIP: lock_is_held_type+0x35/0x210 kernel/locking/lockdep.c:3951 RSP:
ffff8801db107e50
---[ end trace 72e22e44a48160ef ]---
general protection fault: 0000 [#2] SMP KASAN


---
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.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, 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.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

On Mon, Apr 16, 2018 at 3:02 AM, syzbot
<syzbot+fea25d...@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 18b7fd1c93e5204355ddbf2608a097d64df81b88 (Sat Apr 14 15:50:50 2018 +0000)
> Merge branch 'akpm' (patches from Andrew)
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=fea25d0a45f1ac9af2b4
>
> Unfortunately, I don't have any reproducer for this crash yet.
> Raw console output:
> https://syzkaller.appspot.com/x/log.txt?id=4804496370696192
> Kernel config:
> https://syzkaller.appspot.com/x/.config?id=-8852471259444315113
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> CC: [core...@netfilter.org da...@davemloft.net f...@strlen.de
> ho...@verge.net.au j...@ssi.bg kad...@blackhole.kfki.hu
> linux-...@vger.kernel.org lvs-...@vger.kernel.org
> net...@vger.kernel.org netfilt...@vger.kernel.org pa...@netfilter.org
> wen...@linux-vs.org]
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+fea25d...@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.

This looks like something induced by a previous silent memory
corruption. Happened only once.

#syz invalid

> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a114467480908a10569ecc5c9%40google.com.
> For more options, visit https://groups.google.com/d/optout.