syzbot

 sign-in | mailing list | source | docs
🐞 Open [717] 🐞 Fixed [181] 🐞 Invalid [640] 📈 Kernel Health 📈 Bugs/Month 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

WARNING in mutex_destroy

Status: upstream: reported C repro on 2020/09/27 03:37
Reported-by: syzbot+15ba17850c1144dd879c@syzkaller.appspotmail.com
First crash: 1361d, last: 808d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 WARNING in mutex_destroy 31 1075d 1364d 0/1 auto-closed as invalid on 2021/11/07 14:31
linux-4.19 WARNING in mutex_destroy (2) C error 6 772d 793d 0/1 upstream: reported C repro on 2022/04/18 14:36
▶ ▼ Last patch testing requests (4)
Created Duration User Patch Repo Result
2023/02/26 03:32 14m retest repro linux-4.14.y report log
2023/02/26 02:32 14m retest repro linux-4.14.y report log
2022/11/07 09:30 9m retest repro linux-4.14.y report log
2022/11/07 08:30 9m retest repro linux-4.14.y report log
▶ ▼ Fix bisection attempts (11)
Created Duration User Patch Repo Result
2022/05/03 03:40 18m bisect fix linux-4.14.y error job log (0)
2022/04/03 03:10 29m bisect fix linux-4.14.y job log (0) log
2022/03/03 16:45 22m bisect fix linux-4.14.y job log (0) log
2022/02/01 16:22 23m bisect fix linux-4.14.y job log (0) log
2022/01/02 15:54 27m bisect fix linux-4.14.y job log (0) log
2021/12/03 15:30 23m bisect fix linux-4.14.y job log (0) log
2021/11/03 15:01 28m bisect fix linux-4.14.y job log (0) log
2021/10/04 13:32 22m bisect fix linux-4.14.y job log (0) log
2021/09/04 13:05 26m bisect fix linux-4.14.y job log (0) log
2021/08/05 12:44 21m bisect fix linux-4.14.y job log (0) log
2021/07/06 12:16 27m bisect fix linux-4.14.y job log (0) log

Sample crash report:
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8053 at kernel/locking/mutex-debug.c:103 mutex_destroy.cold+0x13/0x1a kernel/locking/mutex-debug.c:103
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8053 Comm: syz-executor180 Not tainted 4.14.235-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:183
 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:mutex_destroy.cold+0x13/0x1a kernel/locking/mutex-debug.c:103
RSP: 0018:ffff88808cd47da8 EFLAGS: 00010286
RAX: 000000000000002a RBX: ffff8880b2c4ea80 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffed10119a8fab
RBP: ffff8880b2c4e900 R08: 000000000000002a R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880b308e4c0 R12: 0000000000000000
R13: ffff8880b2c4ea80 R14: ffff8880b34a6e88 R15: ffff88809dea4cd0
 ww_mutex_destroy include/linux/ww_mutex.h:347 [inline]
 reservation_object_fini include/linux/reservation.h:129 [inline]
 dma_buf_release+0x4be/0x5c0 drivers/dma-buf/dma-buf.c:77
 __fput+0x25f/0x7a0 fs/file_table.c:210
 task_work_run+0x11f/0x190 kernel/task_work.c:113
 tracehook_notify_resume include/linux/tracehook.h:191 [inline]
 exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
 syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
 do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x449f99
RSP: 002b:00007fe507397308 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 00000000004ca458 RCX: 0000000000449f99
RDX: 0000000020000000 RSI: 00000000c00464b4 RDI: 0000000000000006
RBP: 00000000004ca450 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004ca45c
R13: 000000000049a074 R14: 6972642f7665642f R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/06/06 12:16 linux-4.14.y a6b2dae3ee3a 500c2339 .config console log report syz C ci2-linux-4-14 WARNING in mutex_destroy
2021/04/11 17:10 linux-4.14.y 958e517f4e16 6a81331a .config console log report syz ci2-linux-4-14 WARNING in mutex_destroy
2021/05/20 07:06 linux-4.14.y 7d7d1c0ab3eb a343ba6b .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/05/17 07:46 linux-4.14.y 7d7d1c0ab3eb f54a5c09 .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/05/09 09:49 linux-4.14.y 7d7d1c0ab3eb bc5434be .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/05/05 12:13 linux-4.14.y 7d7d1c0ab3eb 06c27ff5 .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/03/30 13:31 linux-4.14.y bd634aa64163 6a81331a .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/02/04 02:31 linux-4.14.y 2c8a3fceddf0 624dad51 .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/02/02 23:16 linux-4.14.y 2c8a3fceddf0 624dad51 .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/01/28 19:21 linux-4.14.y 2d2791fce891 7df34f59 .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/01/27 19:08 linux-4.14.y 2d2791fce891 a57db36f .config console log report info ci2-linux-4-14 WARNING in mutex_destroy
2021/01/17 08:32 linux-4.14.y f79dc86058bc 65a7a854 .config console log report info ci2-linux-4-14
2020/09/27 03:36 linux-4.14.y cbfa1702aaf6 5dd8aee8 .config console log report info ci2-linux-4-14
* Struck through repros no longer work on HEAD.