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@xxxxxxxxxxxxx
