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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 354DEC77B73 for ; Sun, 30 Apr 2023 06:32:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231742AbjD3GcO (ORCPT ); Sun, 30 Apr 2023 02:32:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58876 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229665AbjD3GcN (ORCPT ); Sun, 30 Apr 2023 02:32:13 -0400 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2EBC3C1 for ; Sat, 29 Apr 2023 23:32:12 -0700 (PDT) Received: from letrec.thunk.org ([76.150.80.181]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 33U6W56Y005819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 30 Apr 2023 02:32:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1682836328; bh=643DuUgAB//cYcsxro4WK5uhMJqgvM367EgOy2Z/Ql4=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ix2qo65UsPkP4+Vgx1NsvAWHRqWBJCBpHgCK2RBPWGsOYQ2ZZwVJZTyrGNzgUBdeK CLU3M4X/pUMVlt4at4pccS+KOU5tvzCHuR9C2sYwUecZTu8YAT2g43dILCxUB4X3mB OJdXOw1ITDeoH+bAiX3UpkfFBY7cvu4Uj3St8kLnq9Yh8WJlZDn8/1b0JMjgTYbItI SqR13hKqihbG5/tAiyVCv1R7reIDNBJl6LFzAKqdGO29L60qGPWCPPwh66f2j6QtQk XuKmjRwyyrISeqvU9nHlwU8JXZWrG0akPcGjoSJVXpfgmDg6QVlxKfbEO3wjOKwAEZ UDjvjxld4yebQ== Received: by letrec.thunk.org (Postfix, from userid 15806) id E3DCC8C023E; Sun, 30 Apr 2023 02:32:04 -0400 (EDT) Date: Sun, 30 Apr 2023 02:32:04 -0400 From: "Theodore Ts'o" To: syzbot Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Subject: Re: INFO: task hung in lock_mount Message-ID: References: <0000000000006de361056b146dbe@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0000000000006de361056b146dbe@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org #syz set subsystems: nilfs Per the information in the dashboard: https://syzkaller.appspot.com/bug?extid=221d75710bde87fa0e97 There is no mention of ext4 anywhere, and nilfs does show up in the stack trace. So why this is marked with the lables "ext4", "nilfs" is a mystery. Fix it.