WARNING: locking bug in vfs

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
linux-4.19	WARNING: locking bug in vfs_write	syz		error	1	928d	1109d	0/1	upstream: reported syz repro on 2021/04/05 08:53

linux-4.19

WARNING: locking bug in vfs_write

syz

error

928d

1109d

0/1

upstream: reported syz repro on 2021/04/05 08:53

Created	Duration	User	Patch	Repo	Result
2023/02/21 02:32	11m	retest repro		linux-4.14.y	report log
2022/10/30 02:30	9m	retest repro		linux-4.14.y	report log

Created

Duration

User

Patch

Repo

Result

2023/02/21 02:32

11m

retest repro

linux-4.14.y

report log

2022/10/30 02:30

retest repro

linux-4.14.y

report log


Created	Duration	User	Repo	Result
2022/04/30 09:14	16m	bisect fix	linux-4.14.y	error job log (0)
2022/03/31 08:40	33m	bisect fix	linux-4.14.y	job log (0) log
2022/02/28 23:05	31m	bisect fix	linux-4.14.y	job log (0) log
2022/01/29 22:32	32m	bisect fix	linux-4.14.y	job log (0) log
2021/12/30 21:42	34m	bisect fix	linux-4.14.y	job log (0) log
2021/11/30 21:09	32m	bisect fix	linux-4.14.y	job log (0) log
2021/10/31 20:41	27m	bisect fix	linux-4.14.y	job log (0) log
2021/09/30 23:23	34m	bisect fix	linux-4.14.y	job log (0) log
2021/08/31 22:52	30m	bisect fix	linux-4.14.y	job log (0) log
2021/08/01 22:20	31m	bisect fix	linux-4.14.y	job log (0) log
2021/07/02 21:42	27m	bisect fix	linux-4.14.y	job log (0) log
2021/06/02 21:06	35m	bisect fix	linux-4.14.y	job log (0) log
2021/05/03 20:32	33m	bisect fix	linux-4.14.y	job log (0) log

Bluetooth: hci4 command 0x0419 tx timeout Bluetooth: hci0 command 0x0419 tx timeout Bluetooth: hci2 command 0x0419 tx timeout DEBUG_LOCKS_WARN_ON(depth <= 0) ------------[ cut here ]------------ WARNING: CPU: 0 PID: 12499 at kernel/locking/lockdep.c:3760 __lock_release kernel/locking/lockdep.c:3760 [inline] WARNING: CPU: 0 PID: 12499 at kernel/locking/lockdep.c:3760 lock_release.cold+0x13/0xbf kernel/locking/lockdep.c:4017 Kernel panic - not syncing: panic_on_warn set ... CPU: 0 PID: 12499 Comm: syz-executor.3 Not tainted 4.14.228-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 panic+0x1f9/0x42d kernel/panic.c:183 __warn.cold+0x20/0x44 kernel/panic.c:547 report_bug+0x208/0x250 lib/bug.c:186 fixup_bug arch/x86/kernel/traps.c:177 [inline] fixup_bug arch/x86/kernel/traps.c:172 [inline] do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964 RIP: 0010:__lock_release kernel/locking/lockdep.c:3760 [inline] RIP: 0010:lock_release.cold+0x13/0xbf kernel/locking/lockdep.c:4017 RSP: 0018:ffff88809683fdb0 EFLAGS: 00010086 RAX: 000000000000001f RBX: 1ffff11012d07fb9 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffed1012d07fac RBP: ffff8880998e9050 R08: 000000000000001f R09: 0000000000000000 R10: 0000000000000001 R11: 000000656e040339 R12: ffffffff8186b0ed R13: ffffffff8beb9d40 R14: ffff888099fd8300 R15: 0000000000000000 file_end_write include/linux/fs.h:2726 [inline] vfs_write+0x35d/0x4d0 fs/read_write.c:550 SYSC_write fs/read_write.c:590 [inline] SyS_write+0xf2/0x210 fs/read_write.c:582 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x466459 RSP: 002b:00007f8611543188 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: 00007ffdbbb84cdf R14: 00007f8611543300 R15: 0000000000022000 Kernel Offset: disabled Rebooting in 86400 seconds..