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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9DFAAC4332F for ; Tue, 29 Nov 2022 08:33:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:From:Subject:Message-ID:Date: MIME-Version:Reply-To:Cc:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Owner; bh=jZDYUBhvT2y+YT6QnQdDo4NVLhwmomOyezFJ+4AIDpc=; b=yOL YMxoHizQE8gRBK9dTJ7cyR69LLdaFFSqOdXxdC53wzN7VdnpZT99QQz24N8Js37NSrtUGr8W1fx4/ rkSd3ST3DiSUwzmb31WqILP4olVMkcuTeEm3ZdfRKGH2gkVsUPp4tNKwmb/06pZI0xJoD1W3bsCEv ZzsYZsGTjeWsyTR9htGqA6qzkJswAwbvfVH+5e72b1B4+Sm08rn2AGTd42wkTxwMJ2WsF6WQyBECc dJO4Xhq/UiWtq6b7ZD7ZfE1cEsaBZhJvI3HagCX5I9UePvOcJqYMS2lnWiBfjCxDvamQqidrA4zd/ UseRyJvQpNTnu3C85Dbf4Hvi7lKPdsA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ozw2p-007NrJ-Au; Tue, 29 Nov 2022 08:32:47 +0000 Received: from mail-il1-f199.google.com ([209.85.166.199]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ozw2l-007Noa-QQ for linux-arm-kernel@lists.infradead.org; Tue, 29 Nov 2022 08:32:45 +0000 Received: by mail-il1-f199.google.com with SMTP id d19-20020a056e020c1300b00300b5a12c44so11389755ile.15 for ; Tue, 29 Nov 2022 00:32:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8drAHmGU6BwmVnEdd/I8lvsTrVbit3vP6xzirNTyzVs=; b=d7GRMQp1cenOar6aNW1zYcRBb4Zxo8dNxX38Yzvaog7+3dTSSJtotKuz+lEE1TZrhD zTpElsFyq5piXAO8yeConr+Xl3j3mmXKHG/qCBAES1E8ZwHvYkNlbGdedTWde2Ztx64p DkacT3sgfAs2T9kDBEGOaWugQ/gxS97/6NWNKRztcjP2rfY0EIRPTbDsP6cF5cEEFRUp xytQEDUWc6ieG+i6JQu8tC39ATkmfCJJ/b9yciS+y7Rhem/zcaUoV/lLlypZx5bF/L0F P2rfqE0zGpmBD7RzcJGvl+CK7jZdNyjEBpoW9EVbONZUSixhc20GnQgMi0pOLNhYjVyW pd4A== X-Gm-Message-State: ANoB5pl+XzuzBPPXTi/jQQDlOZl7RzNcTTHErk2Av+3j69odKmfyFSaL /U+FknBTY8o3KHX1Ajjz2plDqDhy95yWdYM3AHIxBPjHRV35 X-Google-Smtp-Source: AA0mqf4sJTukmx5RtIwT5mI6Nm3eUeVknq7pfkf/ULRTpj1qG5CCWZEZXJB8v2fkNlzrK6gcGUd9QRn6zXxA5fC1JdZNIZRBfx3d MIME-Version: 1.0 X-Received: by 2002:a05:6638:597:b0:387:da4c:dba1 with SMTP id a23-20020a056638059700b00387da4cdba1mr13587504jar.35.1669710761720; Tue, 29 Nov 2022 00:32:41 -0800 (PST) Date: Tue, 29 Nov 2022 00:32:41 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d482ba05ee97d4e3@google.com> Subject: [syzbot] INFO: task hung in gfs2_gl_hash_clear (3) From: syzbot To: brauner@kernel.org, broonie@kernel.org, catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, madvenka@linux.microsoft.com, scott@os.amperecomputing.com, syzkaller-bugs@googlegroups.com, will@kernel.org X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221129_003243_877581_2BD8D7EC X-CRM114-Status: UNSURE ( 6.21 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello, syzbot found the following issue on: HEAD commit: 6d464646530f Merge branch 'for-next/core' into for-kernelci 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=167aebbb880000 kernel config: https://syzkaller.appspot.com/x/.config?x=54b747d981acc7b7 dashboard link: https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77 compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16467353880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168c3d03880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/d75f5f77b3a3/disk-6d464646.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/9382f86e4d95/vmlinux-6d464646.xz kernel image: https://storage.googleapis.com/syzbot-assets/cf2b5f0d51dd/Image-6d464646.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/04ef22130add/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com INFO: task syz-executor888:3126 blocked for more than 143 seconds. Not tainted 6.1.0-rc6-syzkaller-32662-g6d464646530f #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor888 state:D stack:0 pid:3126 ppid:3124 flags:0x00000000 Call trace: __switch_to+0x180/0x298 arch/arm64/kernel/process.c:553 context_switch kernel/sched/core.c:5209 [inline] __schedule+0x408/0x594 kernel/sched/core.c:6521 schedule+0x64/0xa4 kernel/sched/core.c:6597 schedule_timeout+0x108/0x1b4 kernel/time/timer.c:1935 gfs2_gl_hash_clear+0xd4/0x1b0 fs/gfs2/glock.c:2263 gfs2_put_super+0x318/0x390 fs/gfs2/super.c:620 generic_shutdown_super+0x94/0x198 fs/super.c:492 kill_block_super+0x30/0x78 fs/super.c:1428 gfs2_kill_sb+0x68/0x78 deactivate_locked_super+0x70/0xe8 fs/super.c:332 deactivate_super+0xd0/0xd4 fs/super.c:363 cleanup_mnt+0x184/0x1c0 fs/namespace.c:1186 __cleanup_mnt+0x20/0x30 fs/namespace.c:1193 task_work_run+0x100/0x148 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] do_notify_resume+0x174/0x1f0 arch/arm64/kernel/signal.c:1127 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline] el0_svc+0x9c/0x150 arch/arm64/kernel/entry-common.c:638 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 Showing all locks held in the system: 1 lock held by rcu_tasks_kthre/11: #0: ffff80000d4a4768 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x3c/0x450 kernel/rcu/tasks.h:507 1 lock held by rcu_tasks_trace/12: #0: ffff80000d4a4db8 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x3c/0x450 kernel/rcu/tasks.h:507 1 lock held by khungtaskd/27: #0: ffff80000d4a4640 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x4/0x48 include/linux/rcupdate.h:303 2 locks held by getty/2759: #0: ffff0000c7d7e098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x28/0x58 drivers/tty/tty_ldisc.c:244 #1: ffff80000f6be2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x19c/0x89c drivers/tty/n_tty.c:2177 1 lock held by syz-executor888/3126: #0: ffff0000cae680e0 (&type->s_umount_key#41){+.+.}-{3:3}, at: deactivate_super+0xc8/0xd4 fs/super.c:362 ============================================= --- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel