WARNING in mutex_destroy

12 views
Skip to first unread message

syzbot

unread,
Sep 24, 2020, 8:08:22 AM9/24/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d09b8017 Linux 4.19.147
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1423d2c3900000
kernel config: https://syzkaller.appspot.com/x/.config?x=47cc70be3c316a0a
dashboard link: https://syzkaller.appspot.com/bug?extid=2e32d65441145226a1c3
compiler: gcc (GCC) 10.1.0-syz 20200507

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
WARNING: CPU: 1 PID: 13208 at kernel/locking/mutex-debug.c:103 mutex_destroy+0xec/0x130 kernel/locking/mutex-debug.c:103
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 13208 Comm: syz-executor.3 Not tainted 4.19.147-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+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 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+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:mutex_destroy+0xec/0x130 kernel/locking/mutex-debug.c:103
Code: 11 38 d0 7c 04 84 d2 75 50 8b 05 af 62 e9 0b 85 c0 0f 85 63 ff ff ff 48 c7 c6 20 23 0b 88 48 c7 c7 60 23 0b 88 e8 ea 82 eb ff <0f> 0b e9 49 ff ff ff 48 c7 c7 20 8b 2d 8d e8 11 14 54 00 e9 2e ff
RSP: 0018:ffff888056bffde0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff888090246640 RCX: 0000000000000000
RDX: 0000000000008aba RSI: ffffffff815b523f RDI: ffffed100ad7ffae
RBP: ffff8880902464c0 R08: 0000000000000000 R09: 0000000000000a36
R10: 0000000000000006 R11: 000000000ceedbcf R12: 0000000000000000
R13: ffff888090246640 R14: ffffffff8dd53fc0 R15: ffff8880a9980620
ww_mutex_destroy include/linux/ww_mutex.h:358 [inline]
reservation_object_fini include/linux/reservation.h:129 [inline]
dma_buf_release+0x5e1/0x6e0 drivers/dma-buf/dma-buf.c:77
__fput+0x2ce/0x8a0 fs/file_table.c:278
task_work_run+0x141/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x269/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x57c/0x670 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45e179
Code: 3d b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fc760d47c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 000000000000c540 RCX: 000000000045e179
RDX: 0000000020000240 RSI: 00000000c00464b4 RDI: 0000000000000004
RBP: 000000000118d028 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cff4
R13: 00007ffe59f0775f R14: 00007fc760d489c0 R15: 000000000118cff4
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

unread,
Sep 26, 2020, 11:37:19 PM9/26/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1563f54b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=15ba17850c1144dd879c
compiler: gcc (GCC) 10.1.0-syz 20200507

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

IPVS: ftp: loaded support on port[0] = 21
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
------------[ cut here ]------------
WARNING: CPU: 0 PID: 14806 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: 14806 Comm: syz-executor.1 Not tainted 4.14.198-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/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x4b kernel/panic.c:547
report_bug+0x208/0x249 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:mutex_destroy.cold+0x13/0x1a kernel/locking/mutex-debug.c:103
RSP: 0018:ffff88805675fda8 EFLAGS: 00010286
RAX: 000000000000002a RBX: ffff8880a47e8a80 RCX: 0000000000000000
RDX: 00000000000002f8 RSI: ffffffff814a4600 RDI: ffffed100acebfab
RBP: ffff8880a47e8900 R08: 000000000000002a R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880a4102100 R12: 0000000000000000
R13: ffff8880a47e8a80 R14: ffffffff8afd0ec0 R15: ffff888094ebd790
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:0x45e179
RSP: 002b:00007f42bccffc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 000000000000c540 RCX: 000000000045e179
RDX: 0000000020000240 RSI: 00000000c00464b4 RDI: 0000000000000004
RBP: 000000000118d028 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cff4
R13: 00007ffc1f4e33ef R14: 00007f42bcd009c0 R15: 000000000118cff4

syzbot

unread,
Apr 11, 2021, 1:10:15 PM4/11/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 958e517f Linux 4.14.230
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1390c77ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cdbb0f19434a286f
dashboard link: https://syzkaller.appspot.com/bug?extid=15ba17850c1144dd879c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f7a745d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15ba17...@syzkaller.appspotmail.com

Bluetooth: hci0 command 0x0409 tx timeout
Bluetooth: hci0 command 0x041b tx timeout
Bluetooth: hci0 command 0x040f tx timeout
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
------------[ cut here ]------------
WARNING: CPU: 0 PID: 10430 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: 10430 Comm: syz-executor.0 Not tainted 4.14.230-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:mutex_destroy.cold+0x13/0x1a kernel/locking/mutex-debug.c:103
RSP: 0018:ffff8880a9607da8 EFLAGS: 00010286
RAX: 000000000000002a RBX: ffff8880a8e67800 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffed10152c0fab
RBP: ffff8880a8e67680 R08: 000000000000002a R09: 0000000000000000
R10: 0000000000000000 R11: ffff888091fce000 R12: 0000000000000000
R13: ffff8880a8e67800 R14: ffffffff8c8e9f20 R15: ffff88809bf6c050
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:0x466459
RSP: 002b:00007f4984b1c188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 000000000056c008 RCX: 0000000000466459
RDX: 0000000020000040 RSI: 00000000c00464b4 RDI: 0000000000000003
RBP: 00000000004bf9fb R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c008
R13: 00007ffcd848b6ff R14: 00007f4984b1c300 R15: 0000000000022000

syzbot

unread,
Jun 6, 2021, 8:16:19 AM6/6/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: a6b2dae3 Linux 4.14.235
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e6d475d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=736a5796d40144b
dashboard link: https://syzkaller.appspot.com/bug?extid=15ba17850c1144dd879c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e0c270300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1396f0ffd00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15ba17...@syzkaller.appspotmail.com

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

syzbot

unread,
Nov 7, 2021, 9:31:18 AM11/7/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages