INFO: task hung in bfs_lookup

4 views
Skip to first unread message

syzbot

unread,
Dec 8, 2022, 2:53:38 AM12/8/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10bb4483880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=81391be6350aac7d5ee5
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+81391b...@syzkaller.appspotmail.com

netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'.
9pnet_virtio: no channels available for device syz
INFO: task syz-executor.1:1706 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D28656 1706 8145 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1016 [inline]
__mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'.
bfs_lookup+0x149/0x2b0 fs/bfs/dir.c:136
__lookup_slow+0x246/0x4a0 fs/namei.c:1672
lookup_slow fs/namei.c:1689 [inline]
walk_component+0x7ac/0xda0 fs/namei.c:1811
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'.
lookup_last fs/namei.c:2274 [inline]
path_lookupat+0x1ff/0x8d0 fs/namei.c:2319
netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'.
UDF-fs: bad mount option "u " or missing value
filename_lookup+0x1ac/0x5a0 fs/namei.c:2349
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'.
user_path_at include/linux/namei.h:57 [inline]
vfs_statx+0x113/0x210 fs/stat.c:185
vfs_stat include/linux/fs.h:3132 [inline]
__do_sys_newstat fs/stat.c:337 [inline]
__se_sys_newstat+0x96/0x120 fs/stat.c:333
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 8 ports detected
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f48917d00d9
Code: Bad RIP value.
RSP: 002b:00007f4887929168 EFLAGS: 00000246 ORIG_RAX: 0000000000000004
RAX: ffffffffffffffda RBX: 00007f48918f0050 RCX: 00007f48917d00d9
RDX: 0000000000000000 RSI: 0000000020002d00 RDI: 0000000020002cc0
RBP: 00007f489182bae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff0e30dd5f R14: 00007f4887929300 R15: 0000000000022000

Showing all locks held in the system:
4 locks held by kworker/u4:1/23:
#0: 00000000b6e29252 ((wq_completion)"%s""netns"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 0000000046e350a4 (net_cleanup_work){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000edf34a04 (pernet_ops_rwsem){++++}, at: cleanup_net+0xa8/0x8b0 net/core/net_namespace.c:521
#3: 00000000c703a2b4 (rtnl_mutex){+.+.}, at: ip6gre_exit_batch_net+0x82/0x6c0 net/ipv6/ip6_gre.c:1632
1 lock held by khungtaskd/1570:
#0: 0000000045207d06 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7819:
#0: 000000007bfd5ab4 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by syz-fuzzer/9720:
2 locks held by kworker/1:4/25124:
#0: 00000000cb33c0bc ((wq_completion)"rcu_gp"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 00000000609a38a8 ((work_completion)(&rew.rew_work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
3 locks held by kworker/0:54/31176:
#0: 00000000e319984b ((wq_completion)"%s"("ipv6_addrconf")){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 00000000cb9f811e ((work_completion)(&(&ifa->dad_work)->work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 00000000c703a2b4 (rtnl_mutex){+.+.}, at: addrconf_dad_work+0x9c/0x10a0 net/ipv6/addrconf.c:3989
1 lock held by syz-executor.5/32359:
#0: 000000001a484d34 (rcu_preempt_state.exp_mutex){+.+.}, at: exp_funnel_lock kernel/rcu/tree_exp.h:297 [inline]
#0: 000000001a484d34 (rcu_preempt_state.exp_mutex){+.+.}, at: _synchronize_rcu_expedited+0x4dc/0x6f0 kernel/rcu/tree_exp.h:667
2 locks held by syz-executor.1/1693:
2 locks held by syz-executor.1/1706:
#0: 00000000f6d38f08 (&type->i_mutex_dir_key#18){.+.+}, at: inode_lock_shared include/linux/fs.h:758 [inline]
#0: 00000000f6d38f08 (&type->i_mutex_dir_key#18){.+.+}, at: lookup_slow fs/namei.c:1688 [inline]
#0: 00000000f6d38f08 (&type->i_mutex_dir_key#18){.+.+}, at: walk_component+0x798/0xda0 fs/namei.c:1811
#1: 00000000a3cc1852 (&info->bfs_lock){+.+.}, at: bfs_lookup+0x149/0x2b0 fs/bfs/dir.c:136

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

NMI backtrace for cpu 1
CPU: 1 PID: 1570 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4689 Comm: systemd-journal Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:do_inode_permission fs/namei.c:384 [inline]
RIP: 0010:inode_permission.part.0+0x4e/0x450 fs/namei.c:451
Code: a8 34 bd ff 85 db 0f 85 ee 00 00 00 e8 2b 33 bd ff 4c 8d 75 02 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 0f b6 14 02 <4c> 89 f0 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85 23 03 00 00 44
RSP: 0018:ffff8880a0c67aa0 EFLAGS: 00000a02
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff81a55238
RDX: 0000000000000000 RSI: ffffffff81a55245 RDI: 0000000000000005
RBP: ffff8880a34e7100 R08: ffffffff8cd22848 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880a34e7100
R13: 0000000000000081 R14: ffff8880a34e7102 R15: ffff8880914389a5
FS: 00007f031a4c38c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0317bd0000 CR3: 00000000a0de2000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
inode_permission fs/namei.c:432 [inline]
may_lookup fs/namei.c:1697 [inline]
link_path_walk.part.0+0x1a0/0x1230 fs/namei.c:2085
link_path_walk fs/namei.c:2270 [inline]
path_lookupat+0xe4/0x8d0 fs/namei.c:2318
filename_lookup+0x1ac/0x5a0 fs/namei.c:2349
user_path_at include/linux/namei.h:57 [inline]
do_faccessat+0x248/0x7a0 fs/open.c:397
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f031977e9c7
Code: 83 c4 08 48 3d 01 f0 ff ff 73 01 c3 48 8b 0d c8 d4 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 b8 15 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a1 d4 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007ffeba5fd738 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00007ffeba600760 RCX: 00007f031977e9c7
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00005604475099a3
RBP: 00007ffeba5fd880 R08: 00005604474ff3e5 R09: 0000000000000018
R10: 0000000000000069 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00005604480c08a0 R15: 00007ffeba5fdd70


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

unread,
Apr 7, 2023, 3:53:37 AM4/7/23
to syzkaller...@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