Hello,
syzbot found the following crash on:
HEAD commit: 8fe42840 Merge 4.9.141 into android-4.9
git tree: android-4.9
console output:
https://syzkaller.appspot.com/x/log.txt?x=14ba1373600000
kernel config:
https://syzkaller.appspot.com/x/.config?x=22a5ba9f73b6da1d
dashboard link:
https://syzkaller.appspot.com/bug?extid=00915f625ed10d902364
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=1176a9bb600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+00915f...@syzkaller.appspotmail.com
audit: type=1400 audit(1571413547.896:8): avc: denied { associate } for
pid=2064 comm="syz-executor.4" name="syz4"
scontext=unconfined_u:object_r:unlabeled_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2219 at kernel/locking/rtmutex-debug.c:142
debug_rt_mutex_unlock+0xda/0x100 kernel/locking/rtmutex-debug.c:142
DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current)[ 28.103810] Kernel
panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 2219 Comm: syz-executor.3 Not tainted 4.9.141+ #1
ffff8801cbaf7680 ffffffff81b42e79 ffffffff82a38ce0 00000000ffffffff
ffffffff82a55a00 0000000000000001 0000000000000009 ffff8801cbaf7740
ffffffff813f7125 0000000041b58ab3 ffffffff82e2b62b ffffffff813f6f66
Call Trace:
[<ffffffff81b42e79>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff81b42e79>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
[<ffffffff813f7125>] panic+0x1bf/0x39f kernel/panic.c:179
[<ffffffff813f7362>] __warn.cold.8+0x2f/0x2f kernel/panic.c:542
[<ffffffff810dbec2>] warn_slowpath_fmt+0xc2/0x100 kernel/panic.c:565
[<ffffffff81214bda>] debug_rt_mutex_unlock+0xda/0x100
kernel/locking/rtmutex-debug.c:142
[<ffffffff82811901>] rt_mutex_slowunlock+0x21/0x1c0
kernel/locking/rtmutex.c:1366
[<ffffffff828124ee>] rt_mutex_fastunlock kernel/locking/rtmutex.c:1480
[inline]
[<ffffffff828124ee>] rt_mutex_unlock+0x6e/0xc0
kernel/locking/rtmutex.c:1584
[<ffffffff8129fdec>] exit_pi_state_list+0x34c/0x500 kernel/futex.c:918
[<ffffffff810d2d1e>] mm_release+0x2ee/0x410 kernel/fork.c:1103
[<ffffffff810e6859>] exit_mm kernel/exit.c:469 [inline]
[<ffffffff810e6859>] do_exit+0x399/0x2a50 kernel/exit.c:820
[<ffffffff810ed3a1>] do_group_exit+0x111/0x300 kernel/exit.c:937
[<ffffffff8110eb61>] get_signal+0x4e1/0x1460 kernel/signal.c:2321
[<ffffffff81052aa5>] do_signal+0x95/0x1b00 arch/x86/kernel/signal.c:807
[<ffffffff81003e2e>] exit_to_usermode_loop+0x10e/0x150
arch/x86/entry/common.c:158
[<ffffffff81005932>] prepare_exit_to_usermode arch/x86/entry/common.c:194
[inline]
[<ffffffff81005932>] syscall_return_slowpath arch/x86/entry/common.c:263
[inline]
[<ffffffff81005932>] do_syscall_64+0x3e2/0x550 arch/x86/entry/common.c:290
[<ffffffff82817893>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches