INFO: task hung in packet_release
22 views
Skip to first unread message
syzbot
Apr 13, 2019, 8:02:22 PM4/13/19
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: b859aa7d ANDROID: squashfs: resolve merge conflict with 4...
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=11f2d4d1400000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0bdd1b757a6ba0b
dashboard link: https://syzkaller.appspot.com/bug?extid=59fea288502f5f19cce0
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+59fea2...@syzkaller.appspotmail.com
audit: type=1400 audit(2000000213.825:56608): avc: denied { map } for
pid=31352 comm="blkid" path="/lib/x86_64-linux-gnu/libuuid.so.1.3.0"
dev="sda1" ino=2819 scontext=system_u:system_r:kernel_t:s0
tcontext=system_u:object_r:file_t:s0 tclass=file permissive=1
INFO: task syz-executor4:31269 blocked for more than 140 seconds.
Not tainted 4.14.68+ #4
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor4 D28728 31269 1996 0x80000006
Call Trace:
schedule+0x7f/0x1b0 kernel/sched/core.c:3490
schedule_timeout+0x710/0xe60 kernel/time/timer.c:1718
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x3bc/0x4e0 kernel/sched/completion.c:123
__wait_rcu_gp+0x250/0x3a0 kernel/rcu/update.c:413
synchronize_rcu.part.43+0xd2/0xe0 kernel/rcu/tree_plugin.h:764
synchronize_net+0x3a/0x40 net/core/dev.c:8188
packet_release+0x796/0xb60 net/packet/af_packet.c:3043
__sock_release+0xce/0x250 net/socket.c:602
sock_close+0x15/0x20 net/socket.c:1138
__fput+0x25e/0x6f0 fs/file_table.c:210
task_work_run+0x116/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x8f8/0x2800 kernel/exit.c:865
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:0x410c51
RSP: 002b:00007ffe0c696c20 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000410c51
RDX: 0000000000000000 RSI: 0000000000731308 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000140 R09: ffffffffffffffff
R10: 00000000009301e0 R11: 0000000000000293 R12: 0000000000000006
R13: 00000000001059e6 R14: 00000000000002b7 R15: badc0ffeebadface
Showing all locks held in the system:
1 lock held by khungtaskd/23:
#0: (tasklist_lock){.+.+}, at: [<ffffffff91a019d7>]
debug_show_all_locks+0x74/0x20f kernel/locking/lockdep.c:4541
2 locks held by getty/1906:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9251c980>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff92517eff>]
n_tty_read+0x1ff/0x15e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor4/15142:
#0: (rcu_preempt_state.barrier_mutex){+.+.}, at: [<ffffffff91a47d1b>]
_rcu_barrier+0x5b/0x3f0 kernel/rcu/tree.c:3529
4 locks held by kworker/u4:5/26432:
#0: ("%s""netns"){+.+.}, at: [<ffffffff91927237>]
process_one_work+0x787/0x15c0 kernel/workqueue.c:2085
#1: (net_cleanup_work){+.+.}, at: [<ffffffff9192726f>]
process_one_work+0x7bf/0x15c0 kernel/workqueue.c:2089
#2: (net_mutex){+.+.}, at: [<ffffffff92ad2b1c>] cleanup_net+0x14c/0x880
net/core/net_namespace.c:449
#3: (rcu_preempt_state.barrier_mutex){+.+.}, at: [<ffffffff91a47d1b>]
_rcu_barrier+0x5b/0x3f0 kernel/rcu/tree.c:3529
1 lock held by syz-executor4/31269:
#0: (&sb->s_type->i_mutex_key#9){+.+.}, at: [<ffffffff92a818b4>]
inode_lock include/linux/fs.h:713 [inline]
#0: (&sb->s_type->i_mutex_key#9){+.+.}, at: [<ffffffff92a818b4>]
__sock_release+0x84/0x250 net/socket.c:601
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 23 Comm: khungtaskd Not tainted 4.14.68+ #4
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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 31326 Comm: syz-executor3 Not tainted 4.14.68+ #4
task: ffff8801d185c680 task.stack: ffff8801ceb80000
RIP: 0033:0x4023c4
RSP: 002b:00007f1da022c690 EFLAGS: 00000292
RAX: 00000000c382cc40 RBX: 0000000000000007 RCX: 0000000000457099
RDX: 0000000000000000 RSI: 00007f1da022c6c0 RDI: 0000000000000007
RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d7008 R14: 00000000004ca112 R15: 0000000000000000
FS: 00007f1da022d700(0000) GS:ffff8801dbb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30624000 CR3: 00000001a0ae8006 CR4: 00000000001606a0
---
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 found the following crash on:
HEAD commit: b859aa7d ANDROID: squashfs: resolve merge conflict with 4...
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=11f2d4d1400000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0bdd1b757a6ba0b
dashboard link: https://syzkaller.appspot.com/bug?extid=59fea288502f5f19cce0
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+59fea2...@syzkaller.appspotmail.com
audit: type=1400 audit(2000000213.825:56608): avc: denied { map } for
pid=31352 comm="blkid" path="/lib/x86_64-linux-gnu/libuuid.so.1.3.0"
dev="sda1" ino=2819 scontext=system_u:system_r:kernel_t:s0
tcontext=system_u:object_r:file_t:s0 tclass=file permissive=1
INFO: task syz-executor4:31269 blocked for more than 140 seconds.
Not tainted 4.14.68+ #4
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor4 D28728 31269 1996 0x80000006
Call Trace:
schedule+0x7f/0x1b0 kernel/sched/core.c:3490
schedule_timeout+0x710/0xe60 kernel/time/timer.c:1718
do_wait_for_common kernel/sched/completion.c:91 [inline]
__wait_for_common kernel/sched/completion.c:112 [inline]
wait_for_common+0x3bc/0x4e0 kernel/sched/completion.c:123
__wait_rcu_gp+0x250/0x3a0 kernel/rcu/update.c:413
synchronize_rcu.part.43+0xd2/0xe0 kernel/rcu/tree_plugin.h:764
synchronize_net+0x3a/0x40 net/core/dev.c:8188
packet_release+0x796/0xb60 net/packet/af_packet.c:3043
__sock_release+0xce/0x250 net/socket.c:602
sock_close+0x15/0x20 net/socket.c:1138
__fput+0x25e/0x6f0 fs/file_table.c:210
task_work_run+0x116/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x8f8/0x2800 kernel/exit.c:865
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:0x410c51
RSP: 002b:00007ffe0c696c20 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000410c51
RDX: 0000000000000000 RSI: 0000000000731308 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000140 R09: ffffffffffffffff
R10: 00000000009301e0 R11: 0000000000000293 R12: 0000000000000006
R13: 00000000001059e6 R14: 00000000000002b7 R15: badc0ffeebadface
Showing all locks held in the system:
1 lock held by khungtaskd/23:
#0: (tasklist_lock){.+.+}, at: [<ffffffff91a019d7>]
debug_show_all_locks+0x74/0x20f kernel/locking/lockdep.c:4541
2 locks held by getty/1906:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff9251c980>]
tty_ldisc_ref_wait+0x20/0x80 drivers/tty/tty_ldisc.c:275
#1: (&ldata->atomic_read_lock){+.+.}, at: [<ffffffff92517eff>]
n_tty_read+0x1ff/0x15e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor4/15142:
#0: (rcu_preempt_state.barrier_mutex){+.+.}, at: [<ffffffff91a47d1b>]
_rcu_barrier+0x5b/0x3f0 kernel/rcu/tree.c:3529
4 locks held by kworker/u4:5/26432:
#0: ("%s""netns"){+.+.}, at: [<ffffffff91927237>]
process_one_work+0x787/0x15c0 kernel/workqueue.c:2085
#1: (net_cleanup_work){+.+.}, at: [<ffffffff9192726f>]
process_one_work+0x7bf/0x15c0 kernel/workqueue.c:2089
#2: (net_mutex){+.+.}, at: [<ffffffff92ad2b1c>] cleanup_net+0x14c/0x880
net/core/net_namespace.c:449
#3: (rcu_preempt_state.barrier_mutex){+.+.}, at: [<ffffffff91a47d1b>]
_rcu_barrier+0x5b/0x3f0 kernel/rcu/tree.c:3529
1 lock held by syz-executor4/31269:
#0: (&sb->s_type->i_mutex_key#9){+.+.}, at: [<ffffffff92a818b4>]
inode_lock include/linux/fs.h:713 [inline]
#0: (&sb->s_type->i_mutex_key#9){+.+.}, at: [<ffffffff92a818b4>]
__sock_release+0x84/0x250 net/socket.c:601
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 23 Comm: khungtaskd Not tainted 4.14.68+ #4
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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 31326 Comm: syz-executor3 Not tainted 4.14.68+ #4
task: ffff8801d185c680 task.stack: ffff8801ceb80000
RIP: 0033:0x4023c4
RSP: 002b:00007f1da022c690 EFLAGS: 00000292
RAX: 00000000c382cc40 RBX: 0000000000000007 RCX: 0000000000457099
RDX: 0000000000000000 RSI: 00007f1da022c6c0 RDI: 0000000000000007
RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d7008 R14: 00000000004ca112 R15: 0000000000000000
FS: 00007f1da022d700(0000) GS:ffff8801dbb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30624000 CR3: 00000001a0ae8006 CR4: 00000000001606a0
---
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
Apr 14, 2019, 5:30:18 AM4/14/19
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: aef17a58 Merge 4.9.101 into android-4.9
syzbot found the following crash on:
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=1215a7cf800000
kernel config: https://syzkaller.appspot.com/x/.config?x=c55b447c28981e54
dashboard link: https://syzkaller.appspot.com/bug?extid=84e0c681bfc44cbf759c
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+84e0c6...@syzkaller.appspotmail.com
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:
TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending
cookies. Check SNMP counters.
INFO: task syz-executor0:10178 blocked for more than 120 seconds.
Not tainted 4.9.101-gaef17a5 #32
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor0 D29560 10178 3786 0x00000004
ffff8801ce266000 0000000000000000 ffff8801d6fb4a80 ffff8801d06ab000
ffff8801db221b98 ffff8801d56efa50 ffffffff839e39bd 0000000000000002
0000000041b58ab3 ffffffff843b8b43 00ffffff8121f220 ffff8801db222468
Call Trace:
[<ffffffff839e4fbf>] schedule+0x7f/0x1b0 kernel/sched/core.c:3557
[<ffffffff81280e99>] exp_funnel_lock kernel/rcu/tree_exp.h:279 [inline]
[<ffffffff81280e99>] _synchronize_rcu_expedited+0x689/0x840
kernel/rcu/tree_exp.h:569
[<ffffffff81283be2>] synchronize_rcu_expedited+0x22/0x30
kernel/rcu/tree_exp.h:687
[<ffffffff83069d7f>] synchronize_net+0x2f/0x50 net/core/dev.c:7834
[<ffffffff83686750>] packet_release+0x680/0x9d0 net/packet/af_packet.c:3041
[<ffffffff8300fab6>] sock_release+0x96/0x1c0 net/socket.c:599
[<ffffffff83015db1>] SYSC_socketpair net/socket.c:1369 [inline]
[<ffffffff83015db1>] SyS_socketpair+0x3d1/0x510 net/socket.c:1273
[<ffffffff81006316>] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282
[<ffffffff839f4893>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb
Showing all locks held in the system:
#0: (rcu_read_lock){......}, at: [<ffffffff8136477c>]
check_hung_uninterruptible_tasks kernel/hung_task.c:168 [inline]
#0: (rcu_read_lock){......}, at: [<ffffffff8136477c>]
watchdog+0x11c/0xa20 kernel/hung_task.c:239
#1: (tasklist_lock){.+.+..}, at: [<ffffffff81423c90>]
debug_show_all_locks+0x79/0x218 kernel/locking/lockdep.c:4336
1 lock held by rsyslogd/3597:
#0: (&f->f_pos_lock){+.+.+.}, at: [<ffffffff815d57ac>]
__fdget_pos+0xac/0xd0 fs/file.c:781
2 locks held by getty/3693:
#0: (&tty->ldisc_sem){++++++}, at: [<ffffffff839f2a62>]
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:367
#1: (&ldata->atomic_read_lock){+.+...}, at: [<ffffffff8211cd32>]
n_tty_read+0x202/0x16e0 drivers/tty/n_tty.c:2133
=============================================
NMI backtrace for cpu 0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
ffff8801d8427d08 ffffffff81eb1009 0000000000000000 0000000000000000
0000000000000000 0000000000000001 ffffffff810b7da0 ffff8801d8427d40
ffffffff81ebc307 0000000000000000 0000000000000000 0000000000000003
Call Trace:
[<ffffffff81eb1009>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff81eb1009>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
[<ffffffff81ebc307>] nmi_cpu_backtrace.cold.2+0x48/0x87
lib/nmi_backtrace.c:99
[<ffffffff81ebc29a>] nmi_trigger_cpumask_backtrace+0x12a/0x14f
lib/nmi_backtrace.c:60
[<ffffffff810b7ea4>] arch_trigger_cpumask_backtrace+0x14/0x20
arch/x86/kernel/apic/hw_nmi.c:37
[<ffffffff81364d14>] trigger_all_cpu_backtrace include/linux/nmi.h:58
[inline]
[<ffffffff81364d14>] check_hung_task kernel/hung_task.c:125 [inline]
[<ffffffff81364d14>] check_hung_uninterruptible_tasks
kernel/hung_task.c:182 [inline]
[<ffffffff81364d14>] watchdog+0x6b4/0xa20 kernel/hung_task.c:239
[<ffffffff8119ad9d>] kthread+0x26d/0x300 kernel/kthread.c:211
[<ffffffff839f4a5c>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:373
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at pc 0xffffffff839f34c6
syzbot
May 8, 2019, 12:16:04 AM5/8/19
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
syzbot
Oct 25, 2019, 4:48:05 AM10/25/19
to syzkaller-a...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages