From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 75D30BDC for ; Mon, 3 Jun 2019 05:02:01 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 19B4819B for ; Mon, 3 Jun 2019 05:02:01 +0000 (UTC) Date: Mon, 3 Jun 2019 08:01:57 +0300 From: Leon Romanovsky To: Shuah Khan Message-ID: <20190603050157.GG5261@mtr-leonro.mtl.com> References: <0bc02b84-4d9a-59a7-e6c6-a3b602adca73@linuxfoundation.org> <1018c8ba-61a0-c024-cd98-3b82ebd710ec@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, May 31, 2019 at 09:56:32AM -0600, Shuah Khan wrote: > On 5/31/19 6:01 AM, Laura Abbott wrote: > > On 5/30/19 7:30 PM, Shuah Khan wrote: > > > I would like to propose a topic to discuss ideas to keep up with Syzbot > > > bugs on an ongoing basis. Good news is, as of this writing, we have 1276 > > > fixed, 86 in moderation, and 62 fix pending. However, there are 523 open > > > bugs. A good number of them have been open for longer than 300 days. > > > > > > The oldest one has been open for 537 days. I plan to take a closer at > > > the open bugs to identify areas that might need more help. > > > > > > I have been sending fixes to some of them as I find time like many other > > > developers. In addition, I included syzbot bug analysis as a required > > > contribution in the Linux Kernel Mentorship Program application process. > > > This is for learning debugging skills as well as getting help towards > > > fixing bugs. It has been successful in getting a few fixes in. My goal > > > is  to make these efforts a bit more structured to focus on areas that > > > need help. > > > > > > There are some challenges, the obvious ones being finding time to > > > analyze, reproduce, and fix. Reproducers are available in many cases, > > > and these bugs can be reproduced. Identifying the right fix and fixing > > > is the overwhelming part with the number of outstanding problems. > > > > > > My objective for this topic is to explore and identify areas that might > > > need help in analyzing and fixing bugs in general and especially the > > > ones that have been open for a while. It would help me channel and focus > > > the Mentorship Program efforts and my efforts to help the areas in need. > > > > > > thanks, > > > -- Shuah > > > > I'm interested in this topic for not just syzbot but other bug trackers > > as well. Fedora gets a steady flow of bugs filed and the three official > > maintainers do their best to review but sometimes things slip through, > > especially if we hit a time when several of us are out or traveling. > > The kernel.org bugzilla also gets a number of bug reports that sometimes > > get lost. I'd love to see if there's a process that could work for syzbot > > and other high volume kernel trackers. > > > > I am hoping we can look at all bugs as well. Syzbot happens to be just a > good starting for me to start this discussion. I would say that single place to see/report/manage all bugs (it can be per-subsystem or for whole kernel) and ability to set priority will do the trick. Maybe, it is worth to integrate syzbot dashboard into kernel bugzilla, at least for priority. Thanks > > thanks, > -- Shuah > > _______________________________________________ > Ksummit-discuss mailing list > Ksummit-discuss@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss