From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: dangers of bots on the mailing lists was Re: divide error in ___bpf_prog_run Date: Wed, 17 Jan 2018 18:35:47 -0800 Message-ID: <1516242947.3045.66.camel@perches.com> References: <001a11405130ff1e9705629eb53c@google.com> <20180117093225.GB20303@amd> <20180117204735.GC6948@thunk.org> <20180118002111.b7ejjd2adunmkooj@ast-mbp.dhcp.thefacebook.com> <20180118010930.GE6948@thunk.org> <1516238297.3045.62.camel@perches.com> <20180118014645.66zlrz3bma6wc4xl@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Theodore Ts'o , Alexei Starovoitov , Dmitry Vyukov , Daniel Borkmann , Pavel Machek , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com To: Eric Biggers Return-path: In-Reply-To: <20180118014645.66zlrz3bma6wc4xl@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, 2018-01-17 at 17:46 -0800, Eric Biggers wrote: > On Wed, Jan 17, 2018 at 05:18:17PM -0800, Joe Perches wrote: > > On Wed, 2018-01-17 at 20:09 -0500, Theodore Ts'o wrote: > > > get_maintainer.pl, which is often not accurate > > > > Examples please. > > > > Well, the primary problem is that place the crash occurs is not necessarily > responsible for the bug. But, syzbot actually does have a file blacklist for > exactly that reason; see > https://github.com/google/syzkaller/blob/master/pkg/report/linux.go#L56 Which has no association to a problem with get_maintainer. > And yes, get_maintainer.pl sometimes isn't accurate even if the offending code > is correctly identified. That's more of a community problem, e.g. people > sometimes don't bother to remove themselves from MAINTAINERS when they quit > maintaining, and sometimes people don't feel responsible enough for a file to > add themselves to MAINTAINERS, even when in practice they are actually taking > most of the patches to it through their tree. Yup, not a get_maintainer problem. There are more than 1800 sections and more than 1200 individual names in the MAINTAINERS file. In practice, there are a few dozen maintainers that are upstream patch paths.