From: Aleksandr Nogikh <nogikh@google.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Chinner <david@fromorbit.com>,
syzbot <syzbot+1fa947e7f09e136925b8@syzkaller.appspotmail.com>,
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
Subject: Re: [syzbot] [xfs?] INFO: task hung in clean_bdev_aliases
Date: Wed, 20 Sep 2023 10:56:56 +0200 [thread overview]
Message-ID: <CANp29Y5yx=F1w2s-jHbz1GVWCbOR_Z-gS488L6ERbWQTAX5dRQ@mail.gmail.com> (raw)
In-Reply-To: <20230908082846.GB9560@lst.de>
#syz set subsystems: iomap
On Fri, Sep 8, 2023 at 10:28 AM Christoph Hellwig <hch@lst.de> wrote:
>
> 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.
>
next prev parent reply other threads:[~2023-09-20 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 5:04 [syzbot] [xfs?] INFO: task hung in clean_bdev_aliases syzbot
2023-09-05 21:14 ` Dave Chinner
2023-09-06 17:20 ` Aleksandr Nogikh
2023-09-06 18:04 ` Darrick J. Wong
2023-09-08 8:28 ` Christoph Hellwig
2023-09-20 8:56 ` Aleksandr Nogikh [this message]
2023-09-21 0:38 ` Dave Chinner
2023-09-17 15:35 ` [syzbot] [block] " syzbot
2023-09-19 14:00 ` Ricardo B. Marliere
2023-09-19 14:38 ` syzbot
2023-09-19 2:52 ` syzbot
2023-09-25 8:51 ` Christoph Hellwig
2023-09-25 8:58 ` syzbot
2023-09-25 9:08 ` Christoph Hellwig
2023-09-25 9:35 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANp29Y5yx=F1w2s-jHbz1GVWCbOR_Z-gS488L6ERbWQTAX5dRQ@mail.gmail.com' \
--to=nogikh@google.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+1fa947e7f09e136925b8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).