Hello,
syzbot found the following crash on:
HEAD commit: 4ed22187 Revert "ANDROID: Revert "arm64: move ELF_ET_DYN_B..
git tree: android-4.14
console output:
https://syzkaller.appspot.com/x/log.txt?x=150d2583400000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7acec4778e485bac
dashboard link:
https://syzkaller.appspot.com/bug?extid=970d2dcfa0db6c36efb9
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+970d2d...@syzkaller.appspotmail.com
ip6_tunnel: ip6tnl1 xmit: Local address not yet configured!
INFO: task syz-executor0:1835 blocked for more than 140 seconds.
Not tainted 4.14.78+ #26
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor0 D27928 1835 1790 0x80000004
Call Trace:
schedule+0x7f/0x1b0 kernel/sched/core.c:3490
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:565 [inline]
rwsem_down_write_failed+0x390/0x730 kernel/locking/rwsem-xadd.c:594
call_rwsem_down_write_failed+0x13/0x20 arch/x86/lib/rwsem.S:105
__down_write arch/x86/include/asm/rwsem.h:126 [inline]
down_write+0x4f/0x90 kernel/locking/rwsem.c:56
i_mmap_lock_write include/linux/fs.h:468 [inline]
unlink_file_vma+0x6e/0xa0 mm/mmap.c:157
free_pgtables+0x7c/0x220 mm/memory.c:630
exit_mmap+0x208/0x420 mm/mmap.c:3069
__mmput kernel/fork.c:929 [inline]
mmput+0xc8/0x350 kernel/fork.c:950
exit_mm kernel/exit.c:544 [inline]
do_exit+0x83b/0x2800 kernel/exit.c:852
do_group_exit+0x100/0x2e0 kernel/exit.c:968
get_signal+0x4e5/0x1470 kernel/signal.c:2348
do_signal+0x8f/0x1660 arch/x86/kernel/signal.c:809
exit_to_usermode_loop+0x116/0x150 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+0x35d/0x4b0 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x41124a
RSP: 002b:00007fff2298b658 EFLAGS: 00000246 ORIG_RAX: 000000000000003d
RAX: fffffffffffffe00 RBX: 0000000000000731 RCX: 000000000041124a
RDX: 0000000040000000 RSI: 00007fff2298b664 RDI: ffffffffffffffff
RBP: 000000000072c988 R08: 000000000000072b R09: 000000000211d940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000010
R13: 0000000000412e50 R14: 0000000000000000 R15: 0000000000000000
Showing all locks held in the system:
1 lock held by khungtaskd/23:
#0: (tasklist_lock){.+.+}, at: [<ffffffff91e02047>]
debug_show_all_locks+0x74/0x20f kernel/locking/lockdep.c:4541
2 locks held by getty/1755:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9292f4c0>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff9292aa3f>]
n_tty_read+0x1ff/0x15e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor0/1835:
#0: (&mapping->i_mmap_rwsem){++++}, at: [<ffffffff920dcebe>]
i_mmap_lock_write include/linux/fs.h:468 [inline]
#0: (&mapping->i_mmap_rwsem){++++}, at: [<ffffffff920dcebe>]
unlink_file_vma+0x6e/0xa0 mm/mmap.c:157
2 locks held by syz-executor1/6462:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9292f4c0>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff9292aa3f>]
n_tty_read+0x1ff/0x15e0 drivers/tty/n_tty.c:2142
2 locks held by syz-executor2/10925:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9292f4c0>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&tty->atomic_write_lock){+.+.}, at: [<ffffffff92914ffb>]
tty_write_lock+0x1b/0x60 drivers/tty/tty_io.c:883
2 locks held by syz-executor2/10928:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9292f4c0>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&tty->atomic_write_lock){+.+.}, at: [<ffffffff92914ffb>]
tty_write_lock+0x1b/0x60 drivers/tty/tty_io.c:883
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 23 Comm: khungtaskd Not tainted 4.14.78+ #26
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x11b lib/dump_stack.c:53
nmi_cpu_backtrace.cold.0+0x47/0x85 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x121/0x146 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:138 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:196 [inline]
watchdog+0x574/0xa70 kernel/hung_task.c:252
kthread+0x348/0x420 kernel/kthread.c:232
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:402
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 31340 Comm: syz-executor5 Not tainted 4.14.78+ #26
task: ffff8801c0a34680 task.stack: ffff880198ad8000
RIP: 0033:0x4015b4
RSP: 002b:00007fb8a4874710 EFLAGS: 00000286
RAX: 000000009ac8f033 RBX: 0000000000000007 RCX: 0000000000457569
RDX: 0000000000457569 RSI: 00007fb8a4874740 RDI: 0000000000000007
RBP: 000000000072bf00 R08: 0000000000000000 R09: 00000000004bd9e6
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000072bf0c
R13: 00007ffd63d991ff R14: 00007fb8a48759c0 R15: 0000000000000000
FS: 00007fb8a4875700(0000) GS:ffff8801dba00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c423d91010 CR3: 0000000181464001 CR4: 00000000001606b0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
---
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.