WARNING in mutex_destroy (2)

8 views
Skip to first unread message

syzbot

unread,
Apr 18, 2022, 10:36:27 AM4/18/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1293d7ef700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c1746b2d21a900678727
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

------------[ cut here ]------------
Restarting kernel threads ... done.
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
WARNING: CPU: 0 PID: 20252 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: 0 PID: 20252 Comm: syz-executor.3 Not tainted 4.19.211-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:183
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:mutex_destroy+0xec/0x130 kernel/locking/mutex-debug.c:103
Code: 11 38 d0 7c 04 84 d2 75 50 8b 05 6f 93 ec 0b 85 c0 0f 85 63 ff ff ff 48 c7 c6 c0 0f 6a 88 48 c7 c7 00 10 6a 88 e8 69 59 a8 06 <0f> 0b e9 49 ff ff ff 48 c7 c7 60 37 24 8d e8 d1 fd 4d 00 e9 2e ff
RSP: 0018:ffff88808ed17de0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8880adf08f00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1011da2fae
RBP: ffff8880adf08d80 R08: 0000000000000000 R09: 00000000000012dd
R10: 0000000000000006 R11: ffffffff8c66501b R12: ffff8880adf08000
R13: ffff8880adf08f00 R14: 000000000000003d R15: ffff88823b297c00
ww_mutex_destroy include/linux/ww_mutex.h:358 [inline]
reservation_object_fini include/linux/reservation.h:129 [inline]
dma_buf_release+0x531/0x630 drivers/dma-buf/dma-buf.c:77
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 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+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fa71f3350e9
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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa71dc89168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 00007fa71f448030 RCX: 00007fa71f3350e9
RDX: 0000000020000140 RSI: 0000000040086409 RDI: 0000000000000003
RBP: 00007fa71f38f08d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc216a736f R14: 00007fa71dc89300 R15: 0000000000022000
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,
Apr 18, 2022, 11:04:21 AM4/18/22
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fc8340f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c1746b2d21a900678727
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a359d0f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173f417cf00000

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock))
WARNING: CPU: 0 PID: 8095 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: 0 PID: 8095 Comm: syz-executor415 Not tainted 4.19.211-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:183
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:mutex_destroy+0xec/0x130 kernel/locking/mutex-debug.c:103
Code: 11 38 d0 7c 04 84 d2 75 50 8b 05 6f 93 ec 0b 85 c0 0f 85 63 ff ff ff 48 c7 c6 c0 0f 6a 88 48 c7 c7 00 10 6a 88 e8 69 59 a8 06 <0f> 0b e9 49 ff ff ff 48 c7 c7 60 37 24 8d e8 d1 fd 4d 00 e9 2e ff
RSP: 0018:ffff8880b4f87de0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8880b37c8600 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10169f0fae
RBP: ffff8880b37c8480 R08: 0000000000000000 R09: 00000000000006dd
R10: 0000000000000006 R11: ffffffff8c66501b R12: 0000000000000000
R13: ffff8880b37c8600 R14: ffff8880b2ac5bc8 R15: ffff8880b5b84820
ww_mutex_destroy include/linux/ww_mutex.h:358 [inline]
reservation_object_fini include/linux/reservation.h:129 [inline]
dma_buf_release+0x531/0x630 drivers/dma-buf/dma-buf.c:77
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 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+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fea6096a179
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fea608f62f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 00007fea609ed438 RCX: 00007fea6096a179
RDX: 0000000020000140 RSI: 0000000040086409 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007fea608f6700 R09: 0000000000000000
R10: 00007fea608f6700 R11: 0000000000000246 R12: 00007ffef8d328fe
R13: 00007fea609ed430 R14: 00007fea609ed43c R15: 00007fea609bb074
Reply all
Reply to author
Forward
0 new messages