On Tue, Aug 14, 2018 at 01:50:20PM -0700, Dmitry Vyukov wrote: > On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields <bfie...@fieldses.org> > 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.
We should probably fix that. There's a tiny bit of lock-related code in that file but it's not at all interesting compared, say, to the code that this bug is hitting.... (Which I have no clue about. send_sigurg_to_task() is getting a bad task? Help.) --b. diff --git a/MAINTAINERS b/MAINTAINERS index 9d5eeff51b5f..a5dca2be8513 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -5541,9 +5541,6 @@ M: Jeff Layton <jlay...@kernel.org> M: "J. Bruce Fields" <bfie...@fieldses.org> L: linux-fsde...@vger.kernel.org S: Maintained -F: include/linux/fcntl.h -F: include/uapi/linux/fcntl.h -F: fs/fcntl.c F: fs/locks.c FILESYSTEMS (VFS and infrastructure)
