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 89DF7EE57E4 for ; Fri, 8 Sep 2023 08:28:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235746AbjIHI3A (ORCPT ); Fri, 8 Sep 2023 04:29:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49052 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231129AbjIHI27 (ORCPT ); Fri, 8 Sep 2023 04:28:59 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0D3321FC6; Fri, 8 Sep 2023 01:28:50 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 80BDF68B05; Fri, 8 Sep 2023 10:28:46 +0200 (CEST) Date: Fri, 8 Sep 2023 10:28:46 +0200 From: Christoph Hellwig To: Aleksandr Nogikh Cc: Dave Chinner , syzbot , djwong@kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com, linux-block@vger.kernel.org, hch@lst.de Subject: Re: [syzbot] [xfs?] INFO: task hung in clean_bdev_aliases Message-ID: <20230908082846.GB9560@lst.de> References: <000000000000e534bb0604959011@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Wed, Sep 06, 2023 at 07:20:15PM +0200, Aleksandr Nogikh wrote: > On Tue, Sep 5, 2023 at 11:14 PM 'Dave Chinner' via syzkaller-bugs > wrote: > > > > [cc linux-block, Christoph] > > > > Another iomap-blockdev related issue. > > > > #syz set subsystems: block > > > > syzbot developers: Please review how you are classifying subsystems, > > this is the third false XFS classification in 24 hours. > > The reason why syzbot marked this report as xfs is that, per > MAINTAINERS, fs/iomap/ points to linux-xfs@vger.kernel.org. I can > adjust the rules syzbot uses so that these are routed to "block". > > But should MAINTAINERS actually also not relate IOMAP FILESYSTEM > LIBRARY with xfs in this case? I'd tag it with iomap, as it's a different subsystem just sharing the mailing list. We also have iommu@lists.linux.dev for both the iommu and dma-mapping subsystems as a similar example. But what's also important for issues like this is that often the called library code (in this case iomap) if often not, or only partially at fault. So capturing the calling context (in this case block) might also be useful. And to get out of these meta discussions: I'll look into the actual issues in a bit, I'll try to find time despite travelling.