From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 44AA7C47DDB for ; Mon, 29 Jan 2024 17:31:49 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9C57E6B007D; Mon, 29 Jan 2024 12:31:48 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 94E496B0081; Mon, 29 Jan 2024 12:31:48 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 815E36B0083; Mon, 29 Jan 2024 12:31:48 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 6F09D6B007D for ; Mon, 29 Jan 2024 12:31:48 -0500 (EST) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 1095EA0991 for ; Mon, 29 Jan 2024 17:31:48 +0000 (UTC) X-FDA: 81733041096.05.485826A Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) by imf05.hostedemail.com (Postfix) with ESMTP id 19A2B100024 for ; Mon, 29 Jan 2024 17:31:44 +0000 (UTC) Authentication-Results: imf05.hostedemail.com; dkim=pass header.d=gmail.com header.s=20230601 header.b="G/Mux1bU"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (imf05.hostedemail.com: domain of konishi.ryusuke@gmail.com designates 209.85.167.49 as permitted sender) smtp.mailfrom=konishi.ryusuke@gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1706549505; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=Do+30ZjldJkOOFALkF49apSqQIhe35ps7eq5uqUhCqQ=; b=dOKW11BD3Z59Bi7maM3FE6TOmkMTJDvyYlQiTY59MkD+jHkDAznQJkKdAbFwte3dnlY9ZQ x84BDMRMaItn/kH+aO5Y/ANqt2vIEMm96X1y2XOwSXY3DL7XpM0/se2lmT+fhyBsJk1+nN xwUKAJOBIdQrS3lx0yRCG+KxjS/9XCw= ARC-Authentication-Results: i=1; imf05.hostedemail.com; dkim=pass header.d=gmail.com header.s=20230601 header.b="G/Mux1bU"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (imf05.hostedemail.com: domain of konishi.ryusuke@gmail.com designates 209.85.167.49 as permitted sender) smtp.mailfrom=konishi.ryusuke@gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1706549505; a=rsa-sha256; cv=none; b=t3eTvBjktpPKexkxZSEN+MZxQpv39nDeqpGEJVnD46Zu4JC+9QAgz9UwzntxAIgxFpR+LS pTl9BzvgeqDVkVRR3fq8Sl1mpB4/+2hMgDnI4Lc0dhpqmgrtWCHBtIK7HXY/w8IEYCEerH rmq/xYYbhTho2JDWWFbNMF+vLLIGCcs= Received: by mail-lf1-f49.google.com with SMTP id 2adb3069b0e04-51117bfd452so293022e87.3 for ; Mon, 29 Jan 2024 09:31:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706549503; x=1707154303; darn=kvack.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Do+30ZjldJkOOFALkF49apSqQIhe35ps7eq5uqUhCqQ=; b=G/Mux1bUch6v1G/b76mNH4/+Tyqm8uS+J8voddPjZQBguAiZekzGJsbCDbvA7ihRyT GyKTtdyAli1J4i7Jlrf42cQ+Y6Vv9/n8FalUAb9YQJ5Xrhm5eYSonDcrwdL/xkBOs2XI 4ZHP0uusys91wy+k3D5E8GXcJsdXORzhdmUhB4qJf7vqK8Z/hBDl2ZsPZqdYnfh6eKD4 sGS0Aa4BRytg8nNhe9jdGYRE7rV3gFgGk1kJ+A0L4vUu8hDJxF9EQIcC0xUMgWFM6/L8 bIFwdq5lvmBb3dZwFmFjUVOYFqmJKo5+bqpy4TRt1e9yR7xEPWmBfrYFFL2vw2ZK/xZF nb2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706549503; x=1707154303; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Do+30ZjldJkOOFALkF49apSqQIhe35ps7eq5uqUhCqQ=; b=io+6TkgCw99qltEa6m4zZW8PZfjY26ooBaj0ZBb0IFIXiC972lSMwLamle3VTkqXT1 5Fypa8mAadCEiF4g2l0v5ELx4PnLBY8YHsiyWHYSR0pvCyfNzAKHbNERf02CxnxtRK7K AlzE4qFcSwYr3dfbSzYSLeOp8O6GFzfgLVfPOSMY8iHkFjAEDF0JnhUcV2fsUUpyL9cI EEd5iVc0SlZ/afvAJCctPS707uJ3jJBfScq5J2QjeLWGCHSaLlmyZqaPk20KIyceaCAP UyG8139Rw/qC/Xl/z+qxHm6cVkOApMkakEpsLZyyXUtda+CEGHGFqyTvoxVGD6Sa8v07 /MZg== X-Gm-Message-State: AOJu0YyEq+2AWAOrrzgnGrAfoTPWZPBgT+Uk8KeW8CNCMq68oMx7M6Cj ObMYAUQKCJ7QdIuJh1n19VQMA5PRYRjnbDVayvYM1DGu9R7zSbLfKhzSo9g1NhNNB6tLqFuT34x I4hZENkPBc/vzussnO7ywKXdmCtg= X-Google-Smtp-Source: AGHT+IFLzBH2fvhEsoU+Ej+vPJtfZDQEZY0q0N2YVNdijcR+H+XqmXGS5K8vJa0o39r/ucRoCdt+9GJLIbTg06vavnw= X-Received: by 2002:ac2:4911:0:b0:510:b1b:5db3 with SMTP id n17-20020ac24911000000b005100b1b5db3mr4808091lfi.67.1706549502982; Mon, 29 Jan 2024 09:31:42 -0800 (PST) MIME-Version: 1.0 References: <00000000000047d819061004ad6c@google.com> In-Reply-To: <00000000000047d819061004ad6c@google.com> From: Ryusuke Konishi Date: Tue, 30 Jan 2024 02:31:25 +0900 Message-ID: Subject: Re: [syzbot] [ext4?] [nilfs?] INFO: task hung in migrate_pages_batch To: syzbot Cc: adilger.kernel@dilger.ca, akpm@linux-foundation.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com, tytso@mit.edu, willy@infradead.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 19A2B100024 X-Rspam-User: X-Rspamd-Server: rspam02 X-Stat-Signature: ytwqs6mtgf9egz4t1gqinjgt36dihyw8 X-HE-Tag: 1706549504-188377 X-HE-Meta: U2FsdGVkX1/4N6PX9ZwANlGUxyptdfzasMIy4JJ6aRflQXWBcnahK7uB4v3mvYz6NPpfuKuak6q+9dClRjKpUv1qrhPZmh5tX4JD09yiFPsbKm5mb3nIFZx7zoGXOyJp/ZdNzC7clXXKdh2lcnx/GTq9TBuT1Zeo8bOtvt/1zhcJnvqD9LdiDKp1QmJxAsd8q3jZ6Ap+9n34yvdwyCsKf0BrDWLXQUtdE9msCmnzwOOyHdM4fofl64NXGt05B0Q1PyEYoCCBpkJm66HnXw20Z/v4lmQcgqWYOwb/gUiLmcA9Ok2uulMYBzzlwJgTSEW3rDzvEgCf0Q4s6goodkqP71/mcA8IPLGQwhN4rRf8F7lcGBXYLI37EIXJD3YblW//EJrQAnSNXJ69IrvxoDlcUtrOHBvelgjJ+uF/UgYeIhscsFwzbWFPPEf0mxdl79vBqV35/74TU99MmmnijOzhktOAa5AscwiFVtBvCFSnptBeOtOXvu8UEiVUO0ndfqE/MDpuBGco3nL46NYjct8J8NObjgEHT+hFTbcdNXCyE4qDl4jYmG+WgUMHllq4PYuoPKqsoZF2DX6KOF8I32VlM3gM3VHCx3Iz3uBmr3EKtcn+bfDmf2l+u5LfyIYKAcLWt3/8YbZJA/GV3Ad0oKxrvS9Qe00A4V6sxgBYcgh2IMuX6n/urWL5WeshKT132zFwzEzErcpk7OoAM6+AyUggeIjNI3Qm4wbug2phvTo0im/v5FR+OK3kYuonCQZt1q3g2xqdewwT/TALuwyLJbcaxn22MERklrM5quV72NmN+26wfQA+o/O7YflKP1AVq5GrcORqWIGrf8yPo4dvwrlfIr3H8HW2gGlObQTSWaZqmvtvndz4libzgrv4oTgr7aBCw+sFGRV/JZrTu+4oFQGyUbMVjs2s5QrqMs/wNu4tlfygYZVmfFyz6WaXGIyTit9dBsmeK42E8cawuuTS3UF x8ouNSNR 9VBETpMrGdLQ2w1VbRrt3RYEChbxAj+Uvsr1dqI//ZKGCorRBkoezcZAquLn+0dz5YTHRiSI39xlqCZDa6s/HMQCJp76bm16/HeTiaVqIlFYYHL5j2b7raIO5fE9wLboqmTLJnulzTduIE7vy6GnUc/1T0uFhxZtvb8jg2VZpPaW32fhzdGlQ6XnT/lxBOI4H3ZYEX07yG0JfMB7R1FhTk6yTar9VqWW0mBxZ709EEN2g1ciS1H7S37tLLqvlF0XyISaspUA+nuIDnZWmLIp4c0HYkdKGGd2QwiA9efyF89ICPMXUXnQ7APdC/XQNR/wugt1icHSy3LmciTzF9ZCYUkRWV8PVZobMO+MXS2lK5kwZJrVtJuxXaxfRlCI5TBfvHAm3v8APE0pvKaLpudBLIBkwja0IQHBeFcIGULLKxcLhKvAow0EjbkSAj2CwtclMg3dDOVxGs1mxyCYpQOU2beKYnfPeICxHIsTHepAvjeBdE7+UZS+abvu+SaOSG3t4AM0bQerMjj/45YvayNqCiGLzkUunBN//8Tw2UucMuHPdzLuDUjOjm7aqlQCSJQ3OiZ1HyTDS4fB4b3tVh7tXSX5UqrR69LfMoa7VVWfWYR5mOWD9DlA6KMYVCCL0Rb8pmXkXaMLOMLoPl3hlh6A2CL+2N/lz7sAlrLrI9TfD3Pnm4cTP/WLoXeXw3kvtjs1jmDAKIYbIiyid0xWHb2R6Lh4b6gnQkFXlAfjDrQkHRQM/lhfkdPOrLrFYODza3ypOCWdacir2aZ2w+ESJKrrSQ8AKQkGzyS2swd+gAyyscr+dVPmnxXQBJkfJlDgQ6waxOTJ9aERWeN6WSLYlzC8JamT/PvGb79+MU7hhVE9kUwcK5C0iS0sYCR8LNucgZ72mrY43RQ6hEif80F09rUcLHNb5n95nczOyVdiWtXjXi3uQYhO3T1LywMJhtzfsx4fEbT1gjvkWDPlOkXyhFLsEcSnU7KCO g+BtS311 8iRb65yuoa4pIz7zpXlBThr3FpRk296TI6S+Eh6qzXiYGsAMOucZsbSq02oA/0LIboUgpMfBnr6ekAuClEVWaWJHJrbDHNKlfmhQGCjf75I6OHMy+ZTCqC30MVXNw1uJFaHD/xcm67dnmdDzHjv0sODfnEcghfTMqMUtH1GRShtiwzbBvBgfV7TPyrzehMc/sEruDITL1aGNgzLeQZ3UFMDHbYGc5JaFBQ1NHGPcWMuxsTIyIDIrMA== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Mon, Jan 29, 2024 at 2:15=E2=80=AFAM syzbot wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 0802e17d9aca Merge branch 'for-next/core' into for-kernel= ci > 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=3D10832107e8000= 0 > kernel config: https://syzkaller.appspot.com/x/.config?x=3Df9616b7e18057= 7ba > dashboard link: https://syzkaller.appspot.com/bug?extid=3Dee2ae68da3b22d0= 4cd8d > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Deb= ian) 2.40 > userspace arch: arm64 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=3D163043bfe80= 000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=3D1306c1e3e8000= 0 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/e84e45f27a78/dis= k-0802e17d.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/a8b16d2fc3b1/vmlinu= x-0802e17d.xz > kernel image: https://storage.googleapis.com/syzbot-assets/4c7ac36b3de1/I= mage-0802e17d.gz.xz > mounted in repro: https://storage.googleapis.com/syzbot-assets/e31cee0eb9= 27/mount_10.gz > > IMPORTANT: if you fix the issue, please add the following tag to the comm= it: > Reported-by: syzbot+ee2ae68da3b22d04cd8d@syzkaller.appspotmail.com > > INFO: task syz-executor439:7446 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7446 tgid:7429 ppid:6155 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > io_schedule+0x8c/0x12c kernel/sched/core.c:8998 > folio_wait_bit_common+0x65c/0xb90 mm/filemap.c:1273 > folio_wait_bit+0x30/0x40 mm/filemap.c:1412 > folio_wait_writeback+0x14c/0x3bc mm/page-writeback.c:3065 > migrate_folio_unmap mm/migrate.c:1191 [inline] > migrate_pages_batch+0xc1c/0x25b0 mm/migrate.c:1680 > migrate_pages_sync mm/migrate.c:1873 [inline] > migrate_pages+0x1bf8/0x3114 mm/migrate.c:1955 > do_mbind mm/mempolicy.c:1344 [inline] > kernel_mbind mm/mempolicy.c:1486 [inline] > __do_sys_mbind mm/mempolicy.c:1560 [inline] > __se_sys_mbind mm/mempolicy.c:1556 [inline] > __arm64_sys_mbind+0x1410/0x18e8 mm/mempolicy.c:1556 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > INFO: task segctord:7440 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:segctord state:D stack:0 pid:7440 tgid:7440 ppid:2 = flags:0x00000008 > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > io_schedule+0x8c/0x12c kernel/sched/core.c:8998 > folio_wait_bit_common+0x65c/0xb90 mm/filemap.c:1273 > __folio_lock+0x2c/0x3c mm/filemap.c:1611 > folio_lock include/linux/pagemap.h:1031 [inline] > nilfs_lookup_dirty_data_buffers+0x2b0/0x7e8 fs/nilfs2/segment.c:727 > nilfs_segctor_scan_file+0x1e4/0xcdc fs/nilfs2/segment.c:1084 > nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1206 [inline] > nilfs_segctor_collect fs/nilfs2/segment.c:1533 [inline] > nilfs_segctor_do_construct+0x16ec/0x6560 fs/nilfs2/segment.c:2081 > nilfs_segctor_construct+0x110/0x768 fs/nilfs2/segment.c:2415 > nilfs_segctor_thread_construct fs/nilfs2/segment.c:2523 [inline] > nilfs_segctor_thread+0x3d4/0xd74 fs/nilfs2/segment.c:2606 > kthread+0x288/0x310 kernel/kthread.c:388 > ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857 > INFO: task syz-executor439:7442 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7442 tgid:7441 ppid:6156 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > wb_wait_for_completion+0x154/0x29c fs/fs-writeback.c:192 > sync_inodes_sb+0x220/0x944 fs/fs-writeback.c:2758 > sync_inodes_one_sb+0x58/0x70 fs/sync.c:77 > iterate_supers+0xd4/0x188 fs/super.c:971 > ksys_sync+0xb4/0x1cc fs/sync.c:102 > __arm64_sys_sync+0x14/0x24 fs/sync.c:113 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > INFO: task syz-executor439:7445 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7445 tgid:7444 ppid:6160 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6835 > 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 > bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > sync_inodes_sb+0x208/0x944 fs/fs-writeback.c:2756 > sync_inodes_one_sb+0x58/0x70 fs/sync.c:77 > iterate_supers+0xd4/0x188 fs/super.c:971 > ksys_sync+0xb4/0x1cc fs/sync.c:102 > __arm64_sys_sync+0x14/0x24 fs/sync.c:113 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > INFO: task syz-executor439:7450 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7450 tgid:7448 ppid:6153 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6835 > 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 > bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > sync_inodes_sb+0x208/0x944 fs/fs-writeback.c:2756 > sync_inodes_one_sb+0x58/0x70 fs/sync.c:77 > iterate_supers+0xd4/0x188 fs/super.c:971 > ksys_sync+0xb4/0x1cc fs/sync.c:102 > __arm64_sys_sync+0x14/0x24 fs/sync.c:113 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > INFO: task syz-executor439:7451 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7451 tgid:7449 ppid:6154 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6835 > 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 > bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > sync_inodes_sb+0x208/0x944 fs/fs-writeback.c:2756 > sync_inodes_one_sb+0x58/0x70 fs/sync.c:77 > iterate_supers+0xd4/0x188 fs/super.c:971 > ksys_sync+0xb4/0x1cc fs/sync.c:102 > __arm64_sys_sync+0x14/0x24 fs/sync.c:113 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > INFO: task syz-executor439:7460 blocked for more than 143 seconds. > Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > task:syz-executor439 state:D stack:0 pid:7460 tgid:7456 ppid:6161 = flags:0x0000000d > Call trace: > __switch_to+0x314/0x560 arch/arm64/kernel/process.c:556 > context_switch kernel/sched/core.c:5376 [inline] > __schedule+0x1354/0x2360 kernel/sched/core.c:6688 > __schedule_loop kernel/sched/core.c:6763 [inline] > schedule+0xb8/0x19c kernel/sched/core.c:6778 > schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6835 > 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 > bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > sync_inodes_sb+0x208/0x944 fs/fs-writeback.c:2756 > sync_inodes_one_sb+0x58/0x70 fs/sync.c:77 > iterate_supers+0xd4/0x188 fs/super.c:971 > ksys_sync+0xb4/0x1cc fs/sync.c:102 > __arm64_sys_sync+0x14/0x24 fs/sync.c:113 > __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] > invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 > el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 > do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 > el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 > el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 > el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 > > Showing all locks held in the system: > 1 lock held by khungtaskd/29: > #0: ffff80008e6c48c0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0= xc/0x44 include/linux/rcupdate.h:300 > 2 locks held by kworker/u4:3/41: > #0: ffff0000c1c3a138 ((wq_completion)writeback){+.+.}-{0:0}, at: process= _one_work+0x560/0x1204 kernel/workqueue.c:2600 > #1: ffff8000943f7c20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0= }, at: process_one_work+0x5a0/0x1204 kernel/workqueue.c:2602 > 2 locks held by getty/5863: > #0: ffff0000d255f0a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+= 0x3c/0x4c drivers/tty/tty_ldsem.c:340 > #1: ffff800094e702f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_r= ead+0x41c/0x1228 drivers/tty/n_tty.c:2201 > 1 lock held by segctord/7440: > #0: ffff0000c7ade2a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_tra= nsaction_lock+0x178/0x33c fs/nilfs2/segment.c:357 > 2 locks held by syz-executor439/7442: > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: __super_l= ock fs/super.c:58 [inline] > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: super_loc= k+0x160/0x328 fs/super.c:117 > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_w= rite_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inode= s_sb+0x208/0x944 fs/fs-writeback.c:2756 > 2 locks held by syz-executor439/7445: > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: __super_l= ock fs/super.c:58 [inline] > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: super_loc= k+0x160/0x328 fs/super.c:117 > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_w= rite_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inode= s_sb+0x208/0x944 fs/fs-writeback.c:2756 > 2 locks held by syz-executor439/7450: > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: __super_l= ock fs/super.c:58 [inline] > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: super_loc= k+0x160/0x328 fs/super.c:117 > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_w= rite_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inode= s_sb+0x208/0x944 fs/fs-writeback.c:2756 > 2 locks held by syz-executor439/7451: > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: __super_l= ock fs/super.c:58 [inline] > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: super_loc= k+0x160/0x328 fs/super.c:117 > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_w= rite_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inode= s_sb+0x208/0x944 fs/fs-writeback.c:2756 > 2 locks held by syz-executor439/7460: > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: __super_l= ock fs/super.c:58 [inline] > #0: ffff0000c5e920e0 (&type->s_umount_key#64){++++}-{3:3}, at: super_loc= k+0x160/0x328 fs/super.c:117 > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_w= rite_wb_switch_rwsem fs/fs-writeback.c:364 [inline] > #1: ffff0000c9d147d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inode= s_sb+0x208/0x944 fs/fs-writeback.c:2756 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > --- > 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 syzbot to run the reproducer, reply with: > #syz test: git://repo/address.git branch-or-commit-hash > If you attach or paste a git patch, syzbot will apply it before testing. > > 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 The hang of this report seems to be due to an issue of nilfs2 side. I will fix it. Ryusuke Konishi