From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8B22825620 for ; Mon, 19 Feb 2024 10:54:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.197 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708340059; cv=none; b=EIB93n+dNDjBdqyR33NRzVXYMR4tWxUHfoMfJS/lBad1fsO+7XlGZZqu+XopYdku1Fiibou1OpUB06sVRi92Ia6FlB6Mth3+oYOF8evnaoVS88cdxeC80B1tbJO2QOtgfqvbAoTKpW/fH4iqaVbT+1YBVCb2jRUjkN5CWaBhFzY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708340059; c=relaxed/simple; bh=vcmWLpsbR5n9RKGU2WnaOKPU7Yuwl2Bb2ZNlUPIMcCI=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=u34TJjnVhCdrsE1MnXHTk9Qblg0WNPFEiCWeRfN61X//nN633UX/99XcGkikfoAdgSGd9xIufjCsLFMhQP5KM7AEZZNZ0FHSvFocYrL8HQzVMhgrWEyf+DUkkmGcH5LM9HL7rfyW0c+GtnIXlibU3/Gtfu1nU9IebuiwwqOqEMU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.197 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f197.google.com with SMTP id e9e14a558f8ab-3651ea5170cso9017745ab.2 for ; Mon, 19 Feb 2024 02:54:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708340056; x=1708944856; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=jk5EspbERIA8uUIF9TL7Tb+L6jCRUl5vlESHpidcuZc=; b=e8pXHfygxIHYI6G1pIo+S6f/eJ2dlahYxd6dMvNCij/10WHFQg7Ez6IcarV1ylx952 76UH8d/A8fFCIyDPO0ETP4m+zq+RWrjgEyqmlxi5p1J/WQ6wzEvnwLG5qF6bXZ7NfOKm 6RfhiJV17v2Mp0Gj4eeWBUQRDiWFsl/Wz7E0pykhYi/NN0A7KvzENfV4K1B8O3A8p+nJ MGZLGFMm+0WxaVpuUV8ebJyuYZotAp9KdXiMOwuLtghsAYnU58btiXMcdlHbiRrTgFZq UHf5DHDqnjzBqzsIFGi0mdPv0W4rOqW8nVGn8gHeuwjrRq0zKwvdN26rIWP2ZCc15TOF MzFQ== X-Forwarded-Encrypted: i=1; AJvYcCUt2LLvlkQNpBo5qGJLJz6oy9CxQ78Cx4ZUAtThEx4DssRv2FKE8q97JQpE0Il2kapeswArPIsw85pC39avZ95yH0r71uF5IrALdC4= X-Gm-Message-State: AOJu0YwQyG4EwBcW4KV1VydyHOR0Ps9zANwbZDcUK5C7HvDC/EY3ZzuE oM2cNjcXXZ4PcMQ/ewLJ7Vu13d3J5I4Onm+ag+0kzPuQa1wlODb8ZjRf2OPpp1+Gb0ZviFlmbqf UxiwYQaEAGUkFQ+btasbaz40MeTi2K2f88GLq5TbblAdGmID2igE/L/w= X-Google-Smtp-Source: AGHT+IHhBF6fp0Jnn7wYY17cmd8VUoh94pZXEYHyQl4ojI/qWuxyam31nMsi1y3qV4CIjdv6lbez3Oc8cN5vk76QJp82TsVGcCzQ Precedence: bulk X-Mailing-List: linux-nilfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1b0f:b0:365:26e3:6e60 with SMTP id i15-20020a056e021b0f00b0036526e36e60mr398541ilv.0.1708340056777; Mon, 19 Feb 2024 02:54:16 -0800 (PST) Date: Mon, 19 Feb 2024 02:54:16 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000003d6c9d0611b9ea2d@google.com> Subject: [syzbot] [nilfs?] INFO: task hung in nilfs_segctor_thread (2) From: syzbot To: konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: f735966ee23c Merge branches 'for-next/reorg-va-space' and .. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=12dbb3dc180000 kernel config: https://syzkaller.appspot.com/x/.config?x=d47605a39da2cf06 dashboard link: https://syzkaller.appspot.com/bug?extid=c8166c541d3971bf6c87 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/bdea2316c4db/disk-f735966e.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/75ba7806a91c/vmlinux-f735966e.xz kernel image: https://storage.googleapis.com/syzbot-assets/208f119d45ed/Image-f735966e.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+c8166c541d3971bf6c87@syzkaller.appspotmail.com INFO: task segctord:26558 blocked for more than 143 seconds. Not tainted 6.8.0-rc3-syzkaller-gf735966ee23c #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:segctord state:D stack:0 pid:26558 tgid:26558 ppid:2 flags:0x00000008 Call trace: __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 context_switch kernel/sched/core.c:5400 [inline] __schedule+0x1498/0x24b4 kernel/sched/core.c:6727 __schedule_loop kernel/sched/core.c:6802 [inline] schedule+0xb8/0x19c kernel/sched/core.c:6817 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6874 rwsem_down_write_slowpath+0xcfc/0x1aa0 kernel/locking/rwsem.c:1178 __down_write_common kernel/locking/rwsem.c:1306 [inline] __down_write kernel/locking/rwsem.c:1315 [inline] down_write+0xb4/0xc0 kernel/locking/rwsem.c:1580 nilfs_transaction_lock+0x178/0x33c fs/nilfs2/segment.c:357 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2523 [inline] nilfs_segctor_thread+0x3cc/0xd78 fs/nilfs2/segment.c:2608 kthread+0x288/0x310 kernel/kthread.c:388 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 Showing all locks held in the system: 1 lock held by khungtaskd/29: #0: ffff80008ee43fc0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:297 2 locks held by getty/5931: #0: ffff0000d82710a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340 #1: ffff800093fe72f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41c/0x1228 drivers/tty/n_tty.c:2201 1 lock held by syz-executor.0/6205: #0: ffff0000d6d12c68 (&pipe->mutex/1){+.+.}-{3:3}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:297 2 locks held by kworker/u4:26/13298: 6 locks held by syz-executor.2/26553: 1 lock held by segctord/26558: #0: ffff00011fc2d2a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x178/0x33c fs/nilfs2/segment.c:357 1 lock held by syz-executor.3/11586: #0: ffff0000c346f8b8 (&nft_net->commit_mutex){+.+.}-{3:3}, at: nf_tables_valid_genid+0x3c/0xd4 net/netfilter/nf_tables_api.c:10624 1 lock held by syz-executor.1/11588: 1 lock held by syz-executor.2/11593: #0: ffff0001485282b8 (&nft_net->commit_mutex){+.+.}-{3:3}, at: nf_tables_valid_genid+0x3c/0xd4 net/netfilter/nf_tables_api.c:10624 1 lock held by syz-executor.4/11594: #0: ffff0000d343fcb8 (&nft_net->commit_mutex){+.+.}-{3:3}, at: nf_tables_valid_genid+0x3c/0xd4 net/netfilter/nf_tables_api.c:10624 4 locks held by syz-executor.0/11595: #0: ffff0001b400ef58 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:559 [inline] #0: ffff0001b400ef58 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1385 [inline] #0: ffff0001b400ef58 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1699 [inline] #0: ffff0001b400ef58 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2e0/0x24b4 kernel/sched/core.c:6643 #1: ffff0001b3ffac88 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x3c0/0x618 kernel/sched/psi.c:988 #2: ffff0001b401cc88 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_change+0x100/0x234 kernel/sched/psi.c:912 #3: ffff0001b401cc88 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_change+0x100/0x234 kernel/sched/psi.c:912 ============================================= --- 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 syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup