From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Fri, 28 Jul 2023 09:20:08 +0100 Subject: [Cluster-devel] [syzbot] [gfs2?] kernel panic: hung_task: blocked tasks (2) In-Reply-To: <00000000000045a44b0601802056@google.com> References: <00000000000045a44b0601802056@google.com> Message-ID: <200478.1690532408@warthog.procyon.org.uk> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit syzbot wrote: > Fixes: 9c8ad7a2ff0b ("uapi, x86: Fix the syscall numbering of the mount API syscalls [ver #2]") This would seem unlikely to be the culprit. It just changes the numbering on the fsconfig-related syscalls. Running the test program on v6.5-rc3, however, I end up with the test process stuck in the D state: INFO: task repro-17687f1aa:5551 blocked for more than 120 seconds. Not tainted 6.5.0-rc3-build3+ #1448 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:repro-17687f1aa state:D stack:0 pid:5551 ppid:5516 flags:0x00004002 Call Trace: __schedule+0x4a7/0x4f1 schedule+0x66/0xa1 schedule_timeout+0x9d/0xd7 ? __next_timer_interrupt+0xf6/0xf6 gfs2_gl_hash_clear+0xa0/0xdc ? sugov_irq_work+0x15/0x15 gfs2_put_super+0x19f/0x1d3 generic_shutdown_super+0x78/0x187 kill_block_super+0x1c/0x32 deactivate_locked_super+0x2f/0x61 cleanup_mnt+0xab/0xcc task_work_run+0x6b/0x80 exit_to_user_mode_prepare+0x76/0xfd syscall_exit_to_user_mode+0x14/0x31 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f89aac31dab RSP: 002b:00007fff43d9b878 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007fff43d9cad8 RCX: 00007f89aac31dab RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007fff43d9b920 RBP: 00007fff43d9c960 R08: 0000000000000000 R09: 0000000000000073 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 00007fff43d9cae8 R14: 0000000000417e18 R15: 00007f89aad51000 David 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 us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 986DAC41513 for ; Fri, 28 Jul 2023 08:20:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1690532422; h=from:from:sender: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:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=lX6YGSoycaJbm4O7Y5pBxQR9v7vV+hm4ON2eudkCo74=; b=E4cdDY4Az9QJbYJhEgDYXovlzever/3ztVt43WkET+BV+ah73k8sHIlR+tSjB3kI5G7sfC 3YI3v0rJMV2l/xOfEnFRX/BAn6O3kVfhACsxf4Hrg/OsG8ADdU9IWXfbr1kLQKcAq0DBEk HxsCVo472uVvB4S6zAt5xt767/rwImA= Received: from mimecast-mx02.redhat.com (66.187.233.73 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-223-P3EhA2CsNxicq_vDEDrEFA-1; Fri, 28 Jul 2023 04:20:19 -0400 X-MC-Unique: P3EhA2CsNxicq_vDEDrEFA-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EC1E22808E62; Fri, 28 Jul 2023 08:20:18 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id DD85D492B02; Fri, 28 Jul 2023 08:20:18 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id A3DDD1946A6A; Fri, 28 Jul 2023 08:20:18 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 631E31946586 for ; Fri, 28 Jul 2023 08:20:10 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id D9EC546A3A7; Fri, 28 Jul 2023 08:20:10 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.131]) by smtp.corp.redhat.com (Postfix) with ESMTP id 87B18492C13; Fri, 28 Jul 2023 08:20:09 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <00000000000045a44b0601802056@google.com> References: <00000000000045a44b0601802056@google.com> To: syzbot MIME-Version: 1.0 Date: Fri, 28 Jul 2023 09:20:08 +0100 Message-ID: <200478.1690532408@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 Subject: Re: [Cluster-devel] [syzbot] [gfs2?] kernel panic: hung_task: blocked tasks (2) X-BeenThere: cluster-devel@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: "\[Cluster devel\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: cluster-devel@redhat.com, arnd@arndb.de, syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org, dhowells@redhat.com, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org Errors-To: cluster-devel-bounces@redhat.com Sender: "Cluster-devel" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-ID: <200477.1690532408.1@warthog.procyon.org.uk> Content-Transfer-Encoding: quoted-printable Message-ID: <20230728082008.Z-UvSU9AKg-Rl28saT5wy89usEB0IwIebnOOmiEFUiQ@z> syzbot wrote: > Fixes: 9c8ad7a2ff0b ("uapi, x86: Fix the syscall numbering of the mount A= PI syscalls [ver #2]") This would seem unlikely to be the culprit. It just changes the numbering = on the fsconfig-related syscalls. Running the test program on v6.5-rc3, however, I end up with the test proce= ss stuck in the D state: INFO: task repro-17687f1aa:5551 blocked for more than 120 seconds. Not tainted 6.5.0-rc3-build3+ #1448 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:repro-17687f1aa state:D stack:0 pid:5551 ppid:5516 flags:0x0000= 4002 Call Trace: __schedule+0x4a7/0x4f1 schedule+0x66/0xa1 schedule_timeout+0x9d/0xd7 ? __next_timer_interrupt+0xf6/0xf6 gfs2_gl_hash_clear+0xa0/0xdc ? sugov_irq_work+0x15/0x15 gfs2_put_super+0x19f/0x1d3 generic_shutdown_super+0x78/0x187 kill_block_super+0x1c/0x32 deactivate_locked_super+0x2f/0x61 cleanup_mnt+0xab/0xcc task_work_run+0x6b/0x80 exit_to_user_mode_prepare+0x76/0xfd syscall_exit_to_user_mode+0x14/0x31 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f89aac31dab RSP: 002b:00007fff43d9b878 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007fff43d9cad8 RCX: 00007f89aac31dab RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007fff43d9b920 RBP: 00007fff43d9c960 R08: 0000000000000000 R09: 0000000000000073 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 00007fff43d9cae8 R14: 0000000000417e18 R15: 00007f89aad51000 David