Hello,
syzbot found the following crash on:
HEAD commit: b11964ad ANDROID: cuttlefish: enable CONFIG_INET_UDP_DIAG=y
git tree: android-4.14
console output:
https://syzkaller.appspot.com/x/log.txt?x=120f1313200000
kernel config:
https://syzkaller.appspot.com/x/.config?x=322dd7397c84f390
dashboard link:
https://syzkaller.appspot.com/bug?extid=e79dcc3616b4360760a0
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=121304cf200000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+e79dcc...@syzkaller.appspotmail.com
random: cc1: uninitialized urandom read (8 bytes read)
audit: type=1400 audit(1552198896.753:10): avc: denied { map } for
pid=1954 comm="syz-execprog" path="/root/syzkaller-shm123699983" dev="sda1"
ino=16482 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:file_t:s0 tclass=file permissive=1
INFO: task blkid:2117 blocked for more than 140 seconds.
Not tainted 4.14.105+ #29
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
blkid D28664 2117 309 0x00000004
Call Trace:
schedule+0x92/0x1c0 kernel/sched/core.c:3492
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:3550
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x559/0x1430 kernel/locking/mutex.c:893
__lo_release drivers/block/loop.c:1644 [inline]
lo_release+0x78/0x190 drivers/block/loop.c:1668
__blkdev_put+0x518/0x6d0 fs/block_dev.c:1791
blkdev_close+0x86/0xb0 fs/block_dev.c:1863
__fput+0x25e/0x700 fs/file_table.c:210
task_work_run+0x118/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x13b/0x160 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:267 [inline]
do_syscall_64+0x372/0x4b0 arch/x86/entry/common.c:294
INFO: task syz-executor.0:2118 blocked for more than 140 seconds.
Not tainted 4.14.105+ #29
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.0 D27272 2118 1968 0x00000004
Call Trace:
schedule+0x92/0x1c0 kernel/sched/core.c:3492
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:3550
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x559/0x1430 kernel/locking/mutex.c:893
blkdev_reread_part+0x1b/0x40 block/ioctl.c:192
loop_reread_partitions+0x72/0x80 drivers/block/loop.c:615
loop_set_status+0xbff/0x11f0 drivers/block/loop.c:1184
INFO: task blkid:2120 blocked for more than 140 seconds.
Not tainted 4.14.105+ #29
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
blkid D28936 2120 310 0x00000004
Call Trace:
schedule+0x92/0x1c0 kernel/sched/core.c:3492
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:3550
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x559/0x1430 kernel/locking/mutex.c:893
lo_open+0x19/0xb0 drivers/block/loop.c:1624
__blkdev_get+0x963/0xf90 fs/block_dev.c:1537
blkdev_get+0x97/0x8b0 fs/block_dev.c:1612
blkdev_open+0x1cc/0x250 fs/block_dev.c:1770
do_dentry_open+0x41b/0xd60 fs/open.c:764
vfs_open+0x105/0x230 fs/open.c:878
do_last fs/namei.c:3455 [inline]
path_openat+0xb6b/0x2b70 fs/namei.c:3597
do_filp_open+0x1a1/0x280 fs/namei.c:3631
do_sys_open+0x2ca/0x590 fs/open.c:1071
do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289
Showing all locks held in the system:
1 lock held by khungtaskd/23:
#0: (tasklist_lock){.+.+}, at: [<ffffffffb7000e0c>]
debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4541
2 locks held by getty/1762:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffffb7b38782>]
tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:275
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffffb7b33ba7>]
n_tty_read+0x1f7/0x1700 drivers/tty/n_tty.c:2156
3 locks held by blkid/2117:
#0: (&bdev->bd_mutex){+.+.}, at: [<ffffffffb74167d1>]
__blkdev_put+0xb1/0x6d0 fs/block_dev.c:1778
#1: (loop_index_mutex){+.+.}, at: [<ffffffffb7bea1d9>]
lo_release+0x19/0x190 drivers/block/loop.c:1667
#2: (loop_ctl_mutex#2){+.+.}, at: [<ffffffffb7bea238>] __lo_release
drivers/block/loop.c:1644 [inline]
#2: (loop_ctl_mutex#2){+.+.}, at: [<ffffffffb7bea238>]
lo_release+0x78/0x190 drivers/block/loop.c:1668
2 locks held by syz-executor.0/2118:
#0: (loop_ctl_mutex/1){+.+.}, at: [<ffffffffb7be87a3>]
lo_ioctl+0x83/0x1970 drivers/block/loop.c:1405
#1: (&bdev->bd_mutex){+.+.}, at: [<ffffffffb791b5ab>]
blkdev_reread_part+0x1b/0x40 block/ioctl.c:192
2 locks held by blkid/2120:
#0: (&bdev->bd_mutex){+.+.}, at: [<ffffffffb7416ee3>]
__blkdev_get+0xf3/0xf90 fs/block_dev.c:1457
#1: (loop_index_mutex){+.+.}, at: [<ffffffffb7be3b99>] lo_open+0x19/0xb0
drivers/block/loop.c:1624
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 23 Comm: khungtaskd Not tainted 4.14.105+ #29
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x10e lib/dump_stack.c:53
nmi_cpu_backtrace.cold+0x47/0x86 lib/nmi_backtrace.c:101
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at pc 0xffffffffb86430b2
---
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