INFO: task hung in do_ip_setsockopt

12 views
Skip to first unread message

syzbot

unread,
Apr 27, 2019, 4:11:08 AM4/27/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: ffa22221 ANDROID: cuttlefish_defconfig: Enable CONFIG_XFRM..
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=14a9d988a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e770c80c00fb51d
dashboard link: https://syzkaller.appspot.com/bug?extid=ea19e8c766a12b31dd53
compiler: gcc (GCC) 9.0.0 20181231 (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+ea19e8...@syzkaller.appspotmail.com

ip6_tunnel: ip6tnl2 xmit: Local address not yet configured!
INFO: task syz-executor.4:20220 blocked for more than 140 seconds.
Not tainted 4.14.113+ #61
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D29592 20220 31890 0x00000004
Call Trace:
schedule+0x92/0x1c0 kernel/sched/core.c:3498
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:3556
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x559/0x1430 kernel/locking/mutex.c:893
do_ip_setsockopt.isra.0+0x106/0x27d0 net/ipv4/ip_sockglue.c:645
ip_setsockopt+0x36/0x90 net/ipv4/ip_sockglue.c:1248
udp_setsockopt+0x45/0x80 net/ipv4/udp.c:2436
ipv6_setsockopt+0x9e/0x130 net/ipv6/ipv6_sockglue.c:920
tcp_setsockopt net/ipv4/tcp.c:2805 [inline]
tcp_setsockopt+0x81/0xc0 net/ipv4/tcp.c:2799
SYSC_setsockopt net/socket.c:1865 [inline]
SyS_setsockopt+0x12b/0x210 net/socket.c:1844
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: [<00000000cb481a7f>]
debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4544
2 locks held by getty/1764:
#0: (&tty->ldisc_sem){++++}, at: [<00000000aa7e694f>]
tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:284
#1: (&ldata->atomic_read_lock){+.+.}, at: [<00000000d9c8fbef>]
n_tty_read+0x1f7/0x1700 drivers/tty/n_tty.c:2156
1 lock held by syz-executor.4/20220:
#0: (rtnl_mutex){+.+.}, at: [<0000000091699d7c>]
do_ip_setsockopt.isra.0+0x106/0x27d0 net/ipv4/ip_sockglue.c:645

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

NMI backtrace for cpu 0
CPU: 0 PID: 23 Comm: khungtaskd Not tainted 4.14.113+ #61
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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 20237 Comm: syz-executor.3 Not tainted 4.14.113+ #61
task: 0000000004bdaf38 task.stack: 0000000032f4aeaa
RIP: 0010:mark_held_locks+0x39/0xf0 kernel/locking/lockdep.c:2838
RSP: 0018:ffff8881c7427eb0 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffff88819c73de00 RCX: 0000000000000000
RDX: 1ffff110338e7cc5 RSI: 0000000000000000 RDI: ffff88819c73e628
RBP: ffffffff8a804f93 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881c7427fd0
R13: ffff88819c73de00 R14: 0000000000000000 R15: 0000000000000000
FS: 00007fece72a9700(0000) GS:ffff8881d7700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f14d0580000 CR3: 00000001c2524005 CR4: 00000000001606a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
__trace_hardirqs_on_caller kernel/locking/lockdep.c:2871 [inline]
trace_hardirqs_on_caller+0x25b/0x540 kernel/locking/lockdep.c:2926
do_syscall_64+0x43/0x4b0 arch/x86/entry/common.c:277
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x458da9
RSP: 002b:00007fece72a8cf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 000000000073c048 RCX: 0000000000458da9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000073c048
RBP: 000000000073c040 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000073c04c
R13: 00007ffc1d10ea5f R14: 00007fece72a99c0 R15: 000000000073c04c
Code: 41 55 49 89 fd 48 81 c7 28 08 00 00 48 89 fa 41 54 48 c1 ea 03 55 53
48 83 ec 08 0f b6 04 02 84 c0 74 08 3c 03 0f 8e 91 00 00 00 <41> 8b 85 28
08 00 00 85 c0 7e 72 8d 2c b5 00 00 00 00 31 db 49


---
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

unread,
Oct 24, 2019, 3:11:05 AM10/24/19
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages