BUG: corrupted list in fsnotify_detach_mark

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cc24401 Linux 4.14.229
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=159ef0e2d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=51785e7f450b788d
dashboard link: https://syzkaller.appspot.com/bug?extid=d168a4cce06badcb093f

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

list_del corruption. next->prev should be ffff8880979d7910, but was ffff8880976b11f8
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:54!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 16618 Comm: systemd-udevd Not tainted 4.14.229-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880b56e4240 task.stack: ffff88822bd38000
RIP: 0010:__list_del_entry_valid.cold+0x48/0x4a lib/list_debug.c:54
RSP: 0018:ffff88822bd3fe58 EFLAGS: 00010282
RAX: 0000000000000054 RBX: ffff8880976b10c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bbbc0 RDI: ffffed10457a7fc1
RBP: ffff8880979d7910 R08: 0000000000000054 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880af7c7010
R13: ffff888000138010 R14: ffff8880979d7918 R15: 0000000000000000
FS: 00007fd0da5238c0(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff90ea3d108 CR3: 000000022da73000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del_init include/linux/list.h:159 [inline]
fsnotify_detach_mark+0xea/0x350 fs/notify/mark.c:348
fsnotify_destroy_mark+0x2a/0x40 fs/notify/mark.c:391
SYSC_inotify_rm_watch fs/notify/inotify/inotify_user.c:750 [inline]
SyS_inotify_rm_watch+0xc4/0x120 fs/notify/inotify/inotify_user.c:725
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fd0d93a3427
RSP: 002b:00007fff6d285b88 EFLAGS: 00000246 ORIG_RAX: 00000000000000ff
RAX: ffffffffffffffda RBX: 000056423e72b730 RCX: 00007fd0d93a3427
RDX: 0000000000000007 RSI: 0000000000005d70 RDI: 0000000000000009
RBP: 0000000000005d70 R08: 000056423e71f1e9 R09: 0000000000000020
R10: 9d9fd71d014acb6e R11: 0000000000000246 R12: 00007fff6d285ca0
R13: 000056423e72b730 R14: 0000000000000003 R15: 000000000000000e
Code: 87 e8 3b f3 f7 ff 0f 0b 4c 89 e2 48 89 ee 48 c7 c7 c0 ec cc 87 e8 27 f3 f7 ff 0f 0b 48 89 ee 48 c7 c7 80 ed cc 87 e8 16 f3 f7 ff <0f> 0b 45 31 e4 e9 5b 7e 10 fc 48 89 ef 48 89 34 24 e8 3c c8 75
RIP: __list_del_entry_valid.cold+0x48/0x4a lib/list_debug.c:54 RSP: ffff88822bd3fe58
---[ end trace b013f2497138fee2 ]---


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