From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Ayushman Dutta <ayushman999@gmail.com>,
chandanrlinux@gmail.com, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: syzkaller@googlegroups.com
Date: Wed, 29 Jun 2022 08:44:53 +1000 [thread overview]
Message-ID: <20220628224453.GL227878@dread.disaster.area> (raw)
In-Reply-To: <Yrt7t2Y1tsgAUFAr@magnolia>
On Tue, Jun 28, 2022 at 03:07:51PM -0700, Darrick J. Wong wrote:
> [+linux-xfs]
>
> On Tue, Jun 28, 2022 at 02:27:36PM -0500, Ayushman Dutta wrote:
> > Kernel Version: 5.10.122
> >
> > Kernel revision: 58a0d94cb56fe0982aa1ce9712e8107d3a2257fe
> >
> > Syzkaller Dashboard report:
> >
> > ------------[ cut here ]------------
> > WARNING: CPU: 1 PID: 8503 at mm/util.c:618 kvmalloc_node+0x15a/0x170
> > mm/util.c:618
>
> No. Do not DM your syzbot reports to random XFS developers.
>
> Especially do not send me *three message* with 300K of attachments; even
> the regular syzbot runners dump all that stuff into a web portal.
>
> If you are going to run some scripted tool to randomly
> corrupt the filesystem to find failures, then you have an
> ethical and moral responsibility to do some of the work to
> narrow down and identify the cause of the failure, not just
> throw them at someone else to do all the work.
/me reads the stack trace, takes 30s to look at the change log,
finds commit 29d650f7e3ab ("xfs: reject crazy array sizes being fed
to XFS_IOC_GETBMAP*").
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-06-28 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+6OtaVMKW=K2mfbi=3A7fuPw2BmHv-zcx2jVKg9yEEY4wab3g@mail.gmail.com>
2022-06-28 22:07 ` syzkaller@googlegroups.com Darrick J. Wong
2022-06-28 22:44 ` Dave Chinner [this message]
2022-06-29 4:32 ` syzkaller@googlegroups.com Amir Goldstein
2022-06-29 16:17 ` syzkaller@googlegroups.com Darrick J. Wong
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=20220628224453.GL227878@dread.disaster.area \
--to=david@fromorbit.com \
--cc=ayushman999@gmail.com \
--cc=chandanrlinux@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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