INFO: task hung in __do_page_fault

6 views
Skip to first unread message

syzbot

unread,
Apr 19, 2019, 4:53:06 AM4/19/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 58b454eb Linux 4.14.112
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12526f5b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b0e7ab7678533ab
dashboard link: https://syzkaller.appspot.com/bug?extid=2b85df964d939e9d4d98
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f2fb2d200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1570432d200000

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

random: sshd: uninitialized urandom read (32 bytes read)
audit: type=1400 audit(1555659832.053:36): avc: denied { map } for
pid=6963 comm="syz-executor108" path="/root/syz-executor108223018"
dev="sda1" ino=1426 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
INFO: task syz-executor108:6975 blocked for more than 140 seconds.
Not tainted 4.14.112 #2
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor108 D28528 6975 6963 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2807 [inline]
__schedule+0x7be/0x1cf0 kernel/sched/core.c:3383
schedule+0x92/0x1c0 kernel/sched/core.c:3427
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:276 [inline]
rwsem_down_read_failed+0x1f4/0x380 kernel/locking/rwsem-xadd.c:293
call_rwsem_down_read_failed+0x18/0x30 arch/x86/lib/rwsem.S:94
__down_read arch/x86/include/asm/rwsem.h:66 [inline]
down_read+0x49/0xb0 kernel/locking/rwsem.c:26
__do_page_fault+0x894/0xb80 arch/x86/mm/fault.c:1361
do_page_fault+0x71/0x515 arch/x86/mm/fault.c:1500
page_fault+0x45/0x50 arch/x86/entry/entry_64.S:1104
RIP: 0033:0x4ab79d
RSP: 002b:00007ffd56766b50 EFLAGS: 00010206
RAX: 00000000004ab8c0 RBX: 0000000000000001 RCX: 00000000006e0330
RDX: 0000000000407620 RSI: 0000000000000000 RDI: 00000000004ccb90
RBP: 00007ffd56766b70 R08: 000000037ffffa00 R09: 000000037ffffa00
R10: 00007ffd56766be0 R11: 0000000000000000 R12: 0000000000000001
R13: 00000000006e0320 R14: 000000000000002d R15: 20c49ba5e353f7cf
INFO: task syz-executor108:6976 blocked for more than 140 seconds.
Not tainted 4.14.112 #2
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor108 D29376 6976 6963 0x80000004
Call Trace:
context_switch kernel/sched/core.c:2807 [inline]
__schedule+0x7be/0x1cf0 kernel/sched/core.c:3383
schedule+0x92/0x1c0 kernel/sched/core.c:3427
__rwsem_down_read_failed_common kernel/locking/rwsem-xadd.c:276 [inline]
rwsem_down_read_failed+0x1f4/0x380 kernel/locking/rwsem-xadd.c:293
call_rwsem_down_read_failed+0x18/0x30 arch/x86/lib/rwsem.S:94
__down_read arch/x86/include/asm/rwsem.h:66 [inline]
down_read+0x49/0xb0 kernel/locking/rwsem.c:26
exit_mm kernel/exit.c:511 [inline]
do_exit+0x3d2/0x2c10 kernel/exit.c:861
do_group_exit+0x111/0x330 kernel/exit.c:977
get_signal+0x348/0x1a80 kernel/signal.c:2407
do_signal+0x86/0x1980 arch/x86/kernel/signal.c:809
exit_to_usermode_loop+0x15c/0x220 arch/x86/entry/common.c:159
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:267 [inline]
do_syscall_64+0x4a9/0x630 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4468f9
RSP: 002b:00007f00a69a4db8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00000000006dbc28 RCX: 00000000004468f9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00000000006dbc28
RBP: 00000000006dbc20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dbc2c
R13: 00007ffd56766b4f R14: 00007f00a69a59c0 R15: 20c49ba5e353f7cf

Showing all locks held in the system:
1 lock held by khungtaskd/1007:
#0: (tasklist_lock){.+.+}, at: [<ffffffff81485f98>]
debug_show_all_locks+0x7f/0x21f kernel/locking/lockdep.c:4544
2 locks held by getty/6939:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6940:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6941:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6942:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6943:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6944:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
2 locks held by getty/6945:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff861a9863>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff831070a6>]
n_tty_read+0x1e6/0x17b0 drivers/tty/n_tty.c:2156
1 lock held by syz-executor108/6975:
#0: (&mm->mmap_sem){++++}, at: [<ffffffff81297f34>]
__do_page_fault+0x894/0xb80 arch/x86/mm/fault.c:1361
1 lock held by syz-executor108/6976:
#0: (&mm->mmap_sem){++++}, at: [<ffffffff813856f2>] exit_mm
kernel/exit.c:511 [inline]
#0: (&mm->mmap_sem){++++}, at: [<ffffffff813856f2>] do_exit+0x3d2/0x2c10
kernel/exit.c:861

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1007 Comm: khungtaskd Not tainted 4.14.112 #2
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+0x138/0x19c lib/dump_stack.c:53
nmi_cpu_backtrace.cold+0x57/0x94 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x141/0x189 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:194 [inline]
watchdog+0x5d8/0xb80 kernel/hung_task.c:250
kthread+0x31c/0x430 kernel/kthread.c:232
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:402
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 6977 Comm: syz-executor108 Not tainted 4.14.112 #2
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff888085a4c300 task.stack: ffff8880a4080000
RIP: 0010:rcu_read_unlock_sched_notrace include/linux/rcupdate.h:777
[inline]
RIP: 0010:trace_lock_release include/trace/events/lock.h:58 [inline]
RIP: 0010:lock_release+0x5f5/0x940 kernel/locking/lockdep.c:4012
RSP: 0018:ffff8880a4087a90 EFLAGS: 00000086
RAX: 0000000000000000 RBX: 1ffff11014810f58 RCX: 1ffffffff0f56320
RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff888085a4cb7c
RBP: ffff8880a4087b28 R08: dffffc0000000000 R09: ffffffff88c882f8
R10: 0000000000000000 R11: ffff888085a4c300 R12: ffff88808a42c5c0
R13: ffffffff816d08de R14: ffff888085a4c300 R15: ffff8880a4087b00
FS: 00007f00a6984700(0000) GS:ffff8880aef00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f00a6983e78 CR3: 00000000897d7000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__mutex_unlock_slowpath+0x71/0x800 kernel/locking/mutex.c:1018
mutex_unlock+0xd/0x10 kernel/locking/mutex.c:614
perf_mmap+0x64e/0x13f0 kernel/events/core.c:5424
call_mmap include/linux/fs.h:1779 [inline]
mmap_region+0x858/0x1030 mm/mmap.c:1722
do_mmap+0x5b8/0xcd0 mm/mmap.c:1500
do_mmap_pgoff include/linux/mm.h:2165 [inline]
vm_mmap_pgoff+0x17a/0x1d0 mm/util.c:333
SYSC_mmap_pgoff mm/mmap.c:1550 [inline]
SyS_mmap_pgoff+0x3ca/0x520 mm/mmap.c:1508
SYSC_mmap arch/x86/kernel/sys_x86_64.c:100 [inline]
SyS_mmap+0x16/0x20 arch/x86/kernel/sys_x86_64.c:91
do_syscall_64+0x1eb/0x630 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4468f9
RSP: 002b:00007f00a6983da8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00000000006dbc38 RCX: 00000000004468f9
RDX: 0000000000000000 RSI: 0000000000003000 RDI: 0000000020ffd000
RBP: 00000000006dbc30 R08: 0000000000000003 R09: 0000000000000000
R10: 0000000000001011 R11: 0000000000000246 R12: 00000000006dbc3c
R13: 00007ffd56766b4f R14: 00007f00a69849c0 R15: 20c49ba5e353f7cf
Code: 65 ff 05 ef b7 b9 7e 48 8b 05 80 39 d9 06 e8 63 e4 04 00 85 c0 74 0d
80 3d cc e4 d8 06 00 0f 84 07 01 00 00 65 ff 0d cb b7 b9 7e <0f> 85 71 fb
ff ff e8 74 0c b8 ff e9 67 fb ff ff 0f 0b 0f 0b 0f


---
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
Reply all
Reply to author
Forward
0 new messages