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 CA77CCE79AB for ; Wed, 20 Sep 2023 08:57:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233861AbjITI5P (ORCPT ); Wed, 20 Sep 2023 04:57:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233860AbjITI5O (ORCPT ); Wed, 20 Sep 2023 04:57:14 -0400 Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EEFF9CA for ; Wed, 20 Sep 2023 01:57:08 -0700 (PDT) Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1c382f23189so145375ad.0 for ; Wed, 20 Sep 2023 01:57:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1695200228; x=1695805028; darn=vger.kernel.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=gCaB4LVQz5Zw5EnS/afR9/bgS309JzKYOV6hPcD95GQ=; b=XNx4NC4GYkaqbHmCT5sap16QyjixxSxYHvkAWz6dTf2l1SPcW0OG4w1jONY4dpuUuR 4E3CtmbJ0XPU+DXO8tL6HhsyfdJLL7H9mkwz4bnIEB7NO9tjbTxENLzK8FM7u42E6pSO i8Qp/oz+56DdF/JfOYwuxQeMEYmpUU4SV/a45da48005fcqb3zdLzID5Nxxc+h7K07T7 OFF/oKoMoTlav2XL9/FWuyz+5AmhyUKfpwjHAT8b+6EHE8S/qzgnfI/PrvTBMOw8+4NY 5XcpfOybZSCGQSbkkYNAFLOj3R0W59ALXFxYU37rrvsxaGnfuFJXr+DzSsXsqlaSCxYg bg4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695200228; x=1695805028; 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=gCaB4LVQz5Zw5EnS/afR9/bgS309JzKYOV6hPcD95GQ=; b=nvaazlm41SeCPDpH+8ed2T9a3flEzAu243O+Hg1cP7Bqnyelo+Ph1PAlGFLU9wq2JO FlcUon3+Ian5ge/ktE3FxDcj/BcK/yyJSdi+2Wqc7Rw6NlFbfV4gEhv/PCrjfEmrBbta bYW0PKhjIxn/xm634GTGjs/F04ux9V/cB1GcDornVV4yMwvpC4rsov3sTvlEi8dKdbUW /chSRTFDFliVyLBm+xONp3GtmmVFgtUz2LLlgu/YnwVOZbJvwC4inJd08ZQ3ZN7OWTuF hHQaMBKCkpChstbmasHlnfutXTSTvufh6Ib203ZhMW2km2PXW1lwFqLLnAKeIf+l2Nnu 8tdA== X-Gm-Message-State: AOJu0Yyoqdcl9CASlV2ar3QPJKhIH+ZDiILG8y7y3BoWAwHfK0tWzd+a RG78y1TZs2mUVE4vlqnuiv7G8nAiT96De6HLrqBYCQ== X-Google-Smtp-Source: AGHT+IG27sQVZz+H2ksdbYnMakCV8uuy/VU9E7xq+vEtRwplNSlDOY8vW8f2mbDcLnt16LsfQVyk9wbzoyZDZ9sWfHk= X-Received: by 2002:a17:903:1c7:b0:1c1:d934:26bc with SMTP id e7-20020a17090301c700b001c1d93426bcmr169727plh.26.1695200228296; Wed, 20 Sep 2023 01:57:08 -0700 (PDT) MIME-Version: 1.0 References: <000000000000e534bb0604959011@google.com> <20230908082846.GB9560@lst.de> In-Reply-To: <20230908082846.GB9560@lst.de> From: Aleksandr Nogikh Date: Wed, 20 Sep 2023 10:56:56 +0200 Message-ID: Subject: Re: [syzbot] [xfs?] INFO: task hung in clean_bdev_aliases To: Christoph Hellwig 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org #syz set subsystems: iomap On Fri, Sep 8, 2023 at 10:28=E2=80=AFAM Christoph Hellwig wrot= e: > > On Wed, Sep 06, 2023 at 07:20:15PM +0200, Aleksandr Nogikh wrote: > > > > 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. >