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=1367ae41880000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link:
https://syzkaller.appspot.com/bug?extid=e07ad170cd11d4d7ef81
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+e07ad1...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
INFO: task segctord:22771 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
segctord D30088 22771 2 0x80000000
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
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:589 [inline]
rwsem_down_write_failed+0x3aa/0x760 kernel/locking/rwsem-xadd.c:618
call_rwsem_down_write_failed+0x13/0x20 arch/x86/lib/rwsem.S:117
__down_write arch/x86/include/asm/rwsem.h:142 [inline]
down_write+0x4f/0x90 kernel/locking/rwsem.c:72
nilfs_transaction_lock+0x1fb/0x8b0 fs/nilfs2/segment.c:362
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2479 [inline]
nilfs_segctor_thread+0x3c0/0xf50 fs/nilfs2/segment.c:2563
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
INFO: task segctord:22829 blocked for more than 140 seconds.
Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
segctord D30320 22829 2 0x80000000
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
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:589 [inline]
rwsem_down_write_failed+0x3aa/0x760 kernel/locking/rwsem-xadd.c:618
call_rwsem_down_write_failed+0x13/0x20 arch/x86/lib/rwsem.S:117
__down_write arch/x86/include/asm/rwsem.h:142 [inline]
down_write+0x4f/0x90 kernel/locking/rwsem.c:72
nilfs_transaction_lock+0x1fb/0x8b0 fs/nilfs2/segment.c:362
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2479 [inline]
nilfs_segctor_thread+0x3c0/0xf50 fs/nilfs2/segment.c:2563
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 00000000d4bd1c35 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7887:
#0: 000000000329f440 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by agetty/8043:
#0: 000000005e8776b8 (&tty->ldisc_sem){++++}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:272
#1: 00000000948f93ea (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x217/0x1950 drivers/tty/n_tty.c:2154
6 locks held by syz-executor.4/22761:
1 lock held by segctord/22771:
#0: 000000006d633e6d (&nilfs->ns_segctor_sem){++++}, at: nilfs_transaction_lock+0x1fb/0x8b0 fs/nilfs2/segment.c:362
5 locks held by syz-executor.3/22821:
1 lock held by segctord/22829:
#0: 0000000059cb8935 (&nilfs->ns_segctor_sem){++++}, at: nilfs_transaction_lock+0x1fb/0x8b0 fs/nilfs2/segment.c:362
3 locks held by kworker/u4:10/27812:
2 locks held by syz-executor.1/8563:
3 locks held by syz-executor.0/8564:
#0: 00000000d90ff802 (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
#0: 00000000d90ff802 (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
IPVS: ftp: loaded support on port[0] = 21
#1: 00000000d4bd1c35 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 00000000d4bd1c35 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
#2: 000000002b0edb20 (&sig->wait_chldexit){....}, at: __wake_up_common_lock+0xb0/0x170 kernel/sched/wait.c:120
IPVS: ftp: loaded support on port[0] = 21
2 locks held by syz-executor.4/8568:
#0: 0000000031378ec2 (pernet_ops_rwsem){++++}, at: copy_net_ns+0x1d8/0x340 net/core/net_namespace.c:435
#1: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: gtp_net_exit+0x1ba/0x380 drivers/net/gtp.c:1360
2 locks held by syz-executor.4/8576:
#0: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: rtnl_lock net/core/rtnetlink.c:77 [inline]
#0: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4779
#1: 000000008fac0dd7 (rcu_preempt_state.exp_mutex){+.+.}, at: exp_funnel_lock kernel/rcu/tree_exp.h:329 [inline]
#1: 000000008fac0dd7 (rcu_preempt_state.exp_mutex){+.+.}, at: _synchronize_rcu_expedited+0x256/0x6f0 kernel/rcu/tree_exp.h:667
2 locks held by syz-executor.4/8582:
#0: 0000000031378ec2 (pernet_ops_rwsem){++++}, at: copy_net_ns+0x1d8/0x340 net/core/net_namespace.c:435
#1: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: gtp_net_exit+0x1ba/0x380 drivers/net/gtp.c:1360
2 locks held by syz-executor.3/8567:
#0: 00000000a2dda670 (&sb->s_type->i_mutex_key#13){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#0: 00000000a2dda670 (&sb->s_type->i_mutex_key#13){+.+.}, at: __sock_release+0x86/0x2a0 net/socket.c:598
#1: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: ip6mr_sk_done+0xe0/0x370 net/ipv6/ip6mr.c:1564
3 locks held by syz-executor.1/8600:
#0: 00000000fde6b05b (cb_lock){++++}, at: genl_rcv+0x15/0x40 net/netlink/genetlink.c:637
#1: 0000000023c96437 (genl_mutex){+.+.}, at: genl_lock net/netlink/genetlink.c:33 [inline]
#1: 0000000023c96437 (genl_mutex){+.+.}, at: genl_rcv_msg+0x12f/0x160 net/netlink/genetlink.c:625
#2: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: tipc_nl_bearer_enable+0x13/0x30 net/tipc/bearer.c:924
1 lock held by syz-executor.2/8606:
#0: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: rtnl_lock net/core/rtnetlink.c:77 [inline]
#0: 0000000044acd3c3 (rtnl_mutex){+.+.}, at: rtnetlink_rcv_msg+0x3fe/0xb80 net/core/rtnetlink.c:4779
3 locks held by syz-executor.0/8610:
FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
=============================================
Enabling of bearer <udp:syz2> rejected, failed to enable media
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: 4698 Comm: systemd-udevd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__list_del_entry_valid+0xb3/0xf0 lib/list_debug.c:54
Code: 14 24 48 39 ea 0f 85 e8 51 85 04 49 8d 7d 08 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 22 49 8b 55 08 <48> 39 ea 0f 85 f9 51 85 04 5d b8 01 00 00 00 41 5c 41 5d c3 e8 44
RSP: 0018:ffff88809b9df7d0 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffffea0002cb5708 RSI: 0000000000000068 RDI: ffffea00011c6110
RBP: ffffea0002cb5708 R08: 0000000000000001 R09: ffffed1027fff788
R10: ffff88813fffbc43 R11: 0000000000000000 R12: ffff88813fffb828
R13: ffffea00011c6108 R14: ffff88813fffb6c0 R15: dffffc0000000000
FS: 00007f90780e98c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc53f92caa5 CR3: 000000009ba3a000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:117 [inline]
list_del include/linux/list.h:125 [inline]
__rmqueue_smallest mm/page_alloc.c:1985 [inline]
__rmqueue mm/page_alloc.c:2475 [inline]
rmqueue mm/page_alloc.c:3034 [inline]
get_page_from_freelist+0x180f/0x4170 mm/page_alloc.c:3373
__alloc_pages_nodemask+0x387/0x2890 mm/page_alloc.c:4399
__alloc_pages include/linux/gfp.h:496 [inline]
__alloc_pages_node include/linux/gfp.h:509 [inline]
kmem_getpages mm/slab.c:1412 [inline]
cache_grow_begin+0xa4/0x8a0 mm/slab.c:2682
cache_alloc_refill+0x273/0x340 mm/slab.c:3049
____cache_alloc mm/slab.c:3132 [inline]
__do_cache_alloc mm/slab.c:3354 [inline]
slab_alloc mm/slab.c:3389 [inline]
kmem_cache_alloc+0x346/0x370 mm/slab.c:3557
getname_flags+0xce/0x590 fs/namei.c:140
user_path_at_empty+0x2a/0x50 fs/namei.c:2609
user_path_at include/linux/namei.h:57 [inline]
vfs_statx+0x113/0x210 fs/stat.c:185
vfs_lstat include/linux/fs.h:3137 [inline]
__do_sys_newlstat fs/stat.c:350 [inline]
__se_sys_newlstat+0x96/0x120 fs/stat.c:344
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f9076f5b335
Code: 69 db 2b 00 64 c7 00 16 00 00 00 b8 ff ff ff ff c3 0f 1f 40 00 83 ff 01 48 89 f0 77 30 48 89 c7 48 89 d6 b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 03 f3 c3 90 48 8b 15 31 db 2b 00 f7 d8 64 89
RSP: 002b:00007ffcda27c068 EFLAGS: 00000246 ORIG_RAX: 0000000000000006
RAX: ffffffffffffffda RBX: 00005625e655c7d0 RCX: 00007f9076f5b335
RDX: 00007ffcda27c0a0 RSI: 00007ffcda27c0a0 RDI: 00005625e655b7d0
RBP: 00007ffcda27c160 R08: 00007f907721a1f8 R09: 0000000000001010
R10: 00007f9077219b58 R11: 0000000000000246 R12: 00005625e655b7d0
R13: 00005625e655b7f0 R14: 00005625e654869b R15: 00005625e65486a0
---
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.