INFO: task hung in tipc_exit_net
4 views
Skip to first unread message
syzbot
Feb 11, 2021, 5:57:19 PM2/11/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 2c8a3fce Linux 4.14.218
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147c1614d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=1a73b0bb8628407f0907
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1a73b0...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
INFO: task kworker/u4:1:22 blocked for more than 140 seconds.
Not tainted 4.14.218-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:1 D27072 22 2 0x80000000
Workqueue: netns cleanup_net
Call Trace:
context_switch syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3384
schedule+0x8d/0x1b0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 syzkaller/managers/linux-4-14/kernel/kernel/time/timer.c:1724
do_wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:91 [inline]
__wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:123
flush_workqueue+0x3ce/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2676
flush_scheduled_work syzkaller/managers/linux-4-14/kernel/./include/linux/workqueue.h:578 [inline]
tipc_exit_net+0x38/0x60 syzkaller/managers/linux-4-14/kernel/net/tipc/core.c:96
ops_exit_list+0xa5/0x150 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:142
cleanup_net+0x3b3/0x840 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:484
process_one_work+0x793/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2250
kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232
ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404
INFO: task syz-executor.4:11910 blocked for more than 140 seconds.
Not tainted 4.14.218-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D27840 11910 8008 0x00000004
Call Trace:
context_switch syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3384
schedule+0x8d/0x1b0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 syzkaller/managers/linux-4-14/kernel/kernel/time/timer.c:1724
do_wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:91 [inline]
__wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:123
flush_work+0x3fe/0x770 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2893
__cancel_work_timer+0x321/0x460 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2964
p9_conn_destroy syzkaller/managers/linux-4-14/kernel/net/9p/trans_fd.c:898 [inline]
p9_fd_close+0x28d/0x420 syzkaller/managers/linux-4-14/kernel/net/9p/trans_fd.c:925
p9_client_create+0x736/0x12c0 syzkaller/managers/linux-4-14/kernel/net/9p/client.c:1095
v9fs_session_init+0x1c5/0x1540 syzkaller/managers/linux-4-14/kernel/fs/9p/v9fs.c:422
v9fs_mount+0x73/0x860 syzkaller/managers/linux-4-14/kernel/fs/9p/vfs_super.c:135
mount_fs+0x92/0x2a0 syzkaller/managers/linux-4-14/kernel/fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:1046
vfs_kern_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:1036 [inline]
do_new_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:2879
SYSC_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465b09
RSP: 002b:00007f71c5db8188 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000056c008 RCX: 0000000000465b09
RDX: 0000000020000080 RSI: 0000000020000300 RDI: 0000000000000000
RBP: 00000000004b069f R08: 0000000020000740 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c008
R13: 00007ffdbf6824df R14: 00007f71c5db8300 R15: 0000000000022000
Showing all locks held in the system:
2 locks held by kworker/0:0/3:
#0: ("events"){+.+.}, at: [<ffffffff81363810>] process_one_work+0x6b0/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2087
#1: ((&m->rq)){+.+.}, at: [<ffffffff81363846>] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091
3 locks held by kworker/u4:1/22:
#0: ("%s""netns"){+.+.}, at: [<ffffffff81363810>] process_one_work+0x6b0/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2087
#1: (net_cleanup_work){+.+.}, at: [<ffffffff81363846>] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091
#2: (net_mutex){+.+.}, at: [<ffffffff85bf6840>] cleanup_net+0x110/0x840 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:450
1 lock held by khungtaskd/1531:
#0: (tasklist_lock){.+.?}, at: [<ffffffff86fedc17>] debug_show_all_locks+0x7c/0x21a syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:4548
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1531 Comm: khungtaskd Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 syzkaller/managers/linux-4-14/kernel/lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x180 syzkaller/managers/linux-4-14/kernel/lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace syzkaller/managers/linux-4-14/kernel/./include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks syzkaller/managers/linux-4-14/kernel/kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 syzkaller/managers/linux-4-14/kernel/kernel/hung_task.c:274
kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232
ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4619 Comm: systemd-journal Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a15f0000 task.stack: ffff8880a15f8000
RIP: 0010:unwind_next_frame+0x2bc/0x17d0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/unwind_orc.c:354
RSP: 0018:ffff8880a15ff7b8 EFLAGS: 00000807
RAX: 0000000000000015 RBX: 1ffff110142bfefe RCX: ffffffff8a72734a
RDX: dffffc0000000000 RSI: ffffffff818613e6 RDI: 1ffffffff14e4e69
RBP: 0000000000000001 R08: ffffffff8a72734e R09: ffffffff8a72734f
R10: 00000000000202a7 R11: 0000000000066071 R12: ffff8880a15ff8ad
R13: ffff8880a15ff8b0 R14: ffff8880a15ff8c8 R15: ffff8880a15ff878
FS: 00007f87cce2b8c0(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f87ca26b000 CR3: 00000000a1b32000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__save_stack_trace+0x90/0x160 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/stacktrace.c:44
save_stack syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:447 [inline]
set_track syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:524
__cache_free syzkaller/managers/linux-4-14/kernel/mm/slab.c:3496 [inline]
kfree+0xc9/0x250 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3815
aa_free_file_ctx syzkaller/managers/linux-4-14/kernel/security/apparmor/include/file.h:76 [inline]
apparmor_file_free_security+0x7e/0xb0 syzkaller/managers/linux-4-14/kernel/security/apparmor/lsm.c:441
security_file_free+0x42/0x80 syzkaller/managers/linux-4-14/kernel/security/security.c:879
put_filp+0x23/0x90 syzkaller/managers/linux-4-14/kernel/fs/file_table.c:307
path_openat+0x6ce/0x2970 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3581
do_filp_open+0x179/0x3c0 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3603
do_sys_open+0x296/0x410 syzkaller/managers/linux-4-14/kernel/fs/open.c:1081
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f87cc3bb840
RSP: 002b:00007fffc2b13cc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007fffc2b13fd0 RCX: 00007f87cc3bb840
RDX: 00000000000001a0 RSI: 0000000000080042 RDI: 000056425a6ee5b0
RBP: 000000000000000d R08: 00000000000001e0 R09: 00000000ffffffff
R10: 0000000000000069 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000056425a6e0040 R14: 00007fffc2b13f90 R15: 000056425a6ed5f0
Code: 00 0f b6 41 04 a8 0f 0f 84 5c 01 00 00 49 8b 77 48 4d 8d 48 01 48 ba 00 00 00 00 00 fc ff df 4c 89 cf 48 c1 ef 03 48 89 74 24 10 <4c> 89 c6 48 c1 ee 03 0f b6 34 16 0f b6 14 17 4c 89 c7 83 e7 07
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: 2c8a3fce Linux 4.14.218
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147c1614d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80e596b8b0902d96
dashboard link: https://syzkaller.appspot.com/bug?extid=1a73b0bb8628407f0907
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1a73b0...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
INFO: task kworker/u4:1:22 blocked for more than 140 seconds.
Not tainted 4.14.218-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:1 D27072 22 2 0x80000000
Workqueue: netns cleanup_net
Call Trace:
context_switch syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3384
schedule+0x8d/0x1b0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 syzkaller/managers/linux-4-14/kernel/kernel/time/timer.c:1724
do_wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:91 [inline]
__wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:123
flush_workqueue+0x3ce/0x1310 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2676
flush_scheduled_work syzkaller/managers/linux-4-14/kernel/./include/linux/workqueue.h:578 [inline]
tipc_exit_net+0x38/0x60 syzkaller/managers/linux-4-14/kernel/net/tipc/core.c:96
ops_exit_list+0xa5/0x150 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:142
cleanup_net+0x3b3/0x840 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:484
process_one_work+0x793/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2250
kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232
ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404
INFO: task syz-executor.4:11910 blocked for more than 140 seconds.
Not tainted 4.14.218-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D27840 11910 8008 0x00000004
Call Trace:
context_switch syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3384
schedule+0x8d/0x1b0 syzkaller/managers/linux-4-14/kernel/kernel/sched/core.c:3428
schedule_timeout+0x80a/0xe90 syzkaller/managers/linux-4-14/kernel/kernel/time/timer.c:1724
do_wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:91 [inline]
__wait_for_common syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:112 [inline]
wait_for_common+0x272/0x430 syzkaller/managers/linux-4-14/kernel/kernel/sched/completion.c:123
flush_work+0x3fe/0x770 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2893
__cancel_work_timer+0x321/0x460 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2964
p9_conn_destroy syzkaller/managers/linux-4-14/kernel/net/9p/trans_fd.c:898 [inline]
p9_fd_close+0x28d/0x420 syzkaller/managers/linux-4-14/kernel/net/9p/trans_fd.c:925
p9_client_create+0x736/0x12c0 syzkaller/managers/linux-4-14/kernel/net/9p/client.c:1095
v9fs_session_init+0x1c5/0x1540 syzkaller/managers/linux-4-14/kernel/fs/9p/v9fs.c:422
v9fs_mount+0x73/0x860 syzkaller/managers/linux-4-14/kernel/fs/9p/vfs_super.c:135
mount_fs+0x92/0x2a0 syzkaller/managers/linux-4-14/kernel/fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:1046
vfs_kern_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:1036 [inline]
do_new_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:2549 [inline]
do_mount+0xe53/0x2a00 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:2879
SYSC_mount syzkaller/managers/linux-4-14/kernel/fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 syzkaller/managers/linux-4-14/kernel/fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465b09
RSP: 002b:00007f71c5db8188 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000056c008 RCX: 0000000000465b09
RDX: 0000000020000080 RSI: 0000000020000300 RDI: 0000000000000000
RBP: 00000000004b069f R08: 0000000020000740 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c008
R13: 00007ffdbf6824df R14: 00007f71c5db8300 R15: 0000000000022000
Showing all locks held in the system:
2 locks held by kworker/0:0/3:
#0: ("events"){+.+.}, at: [<ffffffff81363810>] process_one_work+0x6b0/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2087
#1: ((&m->rq)){+.+.}, at: [<ffffffff81363846>] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091
3 locks held by kworker/u4:1/22:
#0: ("%s""netns"){+.+.}, at: [<ffffffff81363810>] process_one_work+0x6b0/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2087
#1: (net_cleanup_work){+.+.}, at: [<ffffffff81363846>] process_one_work+0x6e6/0x14a0 syzkaller/managers/linux-4-14/kernel/kernel/workqueue.c:2091
#2: (net_mutex){+.+.}, at: [<ffffffff85bf6840>] cleanup_net+0x110/0x840 syzkaller/managers/linux-4-14/kernel/net/core/net_namespace.c:450
1 lock held by khungtaskd/1531:
#0: (tasklist_lock){.+.?}, at: [<ffffffff86fedc17>] debug_show_all_locks+0x7c/0x21a syzkaller/managers/linux-4-14/kernel/kernel/locking/lockdep.c:4548
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1531 Comm: khungtaskd Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 syzkaller/managers/linux-4-14/kernel/lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x180 syzkaller/managers/linux-4-14/kernel/lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace syzkaller/managers/linux-4-14/kernel/./include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks syzkaller/managers/linux-4-14/kernel/kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 syzkaller/managers/linux-4-14/kernel/kernel/hung_task.c:274
kthread+0x30d/0x420 syzkaller/managers/linux-4-14/kernel/kernel/kthread.c:232
ret_from_fork+0x24/0x30 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/entry_64.S:404
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4619 Comm: systemd-journal Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a15f0000 task.stack: ffff8880a15f8000
RIP: 0010:unwind_next_frame+0x2bc/0x17d0 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/unwind_orc.c:354
RSP: 0018:ffff8880a15ff7b8 EFLAGS: 00000807
RAX: 0000000000000015 RBX: 1ffff110142bfefe RCX: ffffffff8a72734a
RDX: dffffc0000000000 RSI: ffffffff818613e6 RDI: 1ffffffff14e4e69
RBP: 0000000000000001 R08: ffffffff8a72734e R09: ffffffff8a72734f
R10: 00000000000202a7 R11: 0000000000066071 R12: ffff8880a15ff8ad
R13: ffff8880a15ff8b0 R14: ffff8880a15ff8c8 R15: ffff8880a15ff878
FS: 00007f87cce2b8c0(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f87ca26b000 CR3: 00000000a1b32000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__save_stack_trace+0x90/0x160 syzkaller/managers/linux-4-14/kernel/arch/x86/kernel/stacktrace.c:44
save_stack syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:447 [inline]
set_track syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:459 [inline]
kasan_slab_free+0xc3/0x1a0 syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:524
__cache_free syzkaller/managers/linux-4-14/kernel/mm/slab.c:3496 [inline]
kfree+0xc9/0x250 syzkaller/managers/linux-4-14/kernel/mm/slab.c:3815
aa_free_file_ctx syzkaller/managers/linux-4-14/kernel/security/apparmor/include/file.h:76 [inline]
apparmor_file_free_security+0x7e/0xb0 syzkaller/managers/linux-4-14/kernel/security/apparmor/lsm.c:441
security_file_free+0x42/0x80 syzkaller/managers/linux-4-14/kernel/security/security.c:879
put_filp+0x23/0x90 syzkaller/managers/linux-4-14/kernel/fs/file_table.c:307
path_openat+0x6ce/0x2970 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3581
do_filp_open+0x179/0x3c0 syzkaller/managers/linux-4-14/kernel/fs/namei.c:3603
do_sys_open+0x296/0x410 syzkaller/managers/linux-4-14/kernel/fs/open.c:1081
do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f87cc3bb840
RSP: 002b:00007fffc2b13cc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007fffc2b13fd0 RCX: 00007f87cc3bb840
RDX: 00000000000001a0 RSI: 0000000000080042 RDI: 000056425a6ee5b0
RBP: 000000000000000d R08: 00000000000001e0 R09: 00000000ffffffff
R10: 0000000000000069 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000056425a6e0040 R14: 00007fffc2b13f90 R15: 000056425a6ed5f0
Code: 00 0f b6 41 04 a8 0f 0f 84 5c 01 00 00 49 8b 77 48 4d 8d 48 01 48 ba 00 00 00 00 00 fc ff df 4c 89 cf 48 c1 ef 03 48 89 74 24 10 <4c> 89 c6 48 c1 ee 03 0f b6 34 16 0f b6 14 17 4c 89 c7 83 e7 07
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Sep 5, 2021, 9:04:19 PM9/5/21
to syzkaller...@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.
Reply all
Reply to author
Forward
0 new messages