syzbot


WARNING: locking bug in vfs_write

Status: upstream: reported syz repro on 2021/04/05 08:53
Reported-by: syzbot+1c1218754d29177420d2@syzkaller.appspotmail.com
First crash: 1338d, last: 1158d
Fix bisection: failed (error log, bisect log)
  
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 WARNING: locking bug in vfs_write syz error 1 978d 1340d 0/1 upstream: reported syz repro on 2021/04/03 20:33
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2021/11/01 12:49 16m bisect fix linux-4.19.y error job log
2021/10/02 12:07 34m bisect fix linux-4.19.y OK (0) job log log
2021/09/02 11:25 41m bisect fix linux-4.19.y OK (0) job log log
2021/08/03 10:46 39m bisect fix linux-4.19.y OK (0) job log log
2021/07/04 10:12 34m bisect fix linux-4.19.y OK (0) job log log
2021/06/04 09:29 42m bisect fix linux-4.19.y OK (0) job log log
2021/05/05 08:52 30m bisect fix linux-4.19.y OK (0) job log log

Sample crash report:
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(depth <= 0)
WARNING: CPU: 1 PID: 9979 at kernel/locking/lockdep.c:3669 __lock_release kernel/locking/lockdep.c:3669 [inline]
WARNING: CPU: 1 PID: 9979 at kernel/locking/lockdep.c:3669 lock_release+0x759/0x8b0 kernel/locking/lockdep.c:3926
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 9979 Comm: syz-executor.0 Not tainted 4.19.184-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+0x1fc/0x2ef lib/dump_stack.c:118
 panic+0x26a/0x50e kernel/panic.c:186
 __warn.cold+0x20/0x5a kernel/panic.c:541
 report_bug+0x262/0x2b0 lib/bug.c:186
 fixup_bug arch/x86/kernel/traps.c:178 [inline]
 fixup_bug arch/x86/kernel/traps.c:173 [inline]
 do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__lock_release kernel/locking/lockdep.c:3669 [inline]
RIP: 0010:lock_release+0x759/0x8b0 kernel/locking/lockdep.c:3926
Code: e9 3f fd ff ff e8 67 5f 05 00 85 c0 0f 85 93 fe ff ff e9 cb b9 a6 06 48 c7 c6 00 4b 6a 88 48 c7 c7 40 19 6a 88 e8 87 1b a6 06 <0f> 0b eb 82 48 89 df e8 4b ee 4c 00 e9 90 fd ff ff e8 41 ee 4c 00
RSP: 0018:ffff88809bbf7d88 EFLAGS: 00010082
RAX: 0000000000000000 RBX: ffffffff8d241760 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814ddd51 RDI: ffffed101377efa3
RBP: ffff888096b48710 R08: 0000000000000000 R09: 00000000000009dd
R10: 0000000000000006 R11: ffffffff8c66305b R12: 1ffff1101377efb4
R13: ffffffff81a27a97 R14: ffff888099798000 R15: 0000000000000000
 file_end_write include/linux/fs.h:2793 [inline]
 vfs_write+0x3d7/0x540 fs/read_write.c:555
 ksys_write+0x12b/0x2a0 fs/read_write.c:599
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x466459
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd04bd58188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000056c0b0 RCX: 0000000000466459
RDX: 0000000020104000 RSI: 0000000020004200 RDI: 0000000000000004
RBP: 00000000004bf9fb R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c0b0
R13: 00007fff78b0654f R14: 00007fd04bd58300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/04/05 08:52 linux-4.19.y 2034d6f0838e 6a81331a .config console log report syz ci2-linux-4-19 WARNING: locking bug in vfs_write
* Struck through repros no longer work on HEAD.