Dmitry Vyukov <dvyukov@xxxxxxxxxx> writes: > On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: >> On Mon, Aug 13, 2018 at 06:33:02AM -0700, syzbot wrote: >>> syzbot has found a reproducer for the following crash on: >>> >>> HEAD commit: 5ed5da74de9e Add linux-next specific files for 20180813 >>> git tree: linux-next >> >> I fetched linux-next but don't have 5ed5da74de9e. > > Hi Bruce, > > +Stephen for the disappeared linux-next commit. > > On the dashboard link you can see that it also happened on a more > recent commit 4e8b38549b50459a22573d756dd1f4e1963c2a8d that I do see > now in linux-next. > >> I'm also not sure why I'm on the cc for this. > > You've been pointed to by "./scripts/get_maintainer.pl -f fs/fcntl.c" > as maintainer of the file, which is the file where the crash happened. You need to use your reproducer to bisect and find the commit that caused this. Otherwise you will continue to confuse people. get_maintainer.pl is not a good target for automated reporting especially against linux-next. Eric
