ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Fri, 31 May 2019 08:01:15 -0400	[thread overview]
Message-ID: <1018c8ba-61a0-c024-cd98-3b82ebd710ec@redhat.com> (raw)
In-Reply-To: <0bc02b84-4d9a-59a7-e6c6-a3b602adca73@linuxfoundation.org>

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.

Thanks,
Laura

  reply	other threads:[~2019-05-31 12:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 23:30 Shuah Khan
2019-05-31 12:01 ` Laura Abbott [this message]
2019-05-31 15:56   ` Shuah Khan
2019-06-03  5:01     ` Leon Romanovsky
2019-05-31 22:15   ` Kees Cook
2019-06-03 10:42     ` Jan Kara
2019-06-04 18:29       ` Laura Abbott
2019-06-03 16:48     ` Shuah Khan
2019-06-02 18:09   ` Sasha Levin
2019-06-03 17:25     ` Shuah Khan
2019-06-03 18:09       ` Konstantin Ryabitsev
2019-06-03 19:32         ` Shuah Khan
2019-06-03 20:48         ` Linus Torvalds
2019-06-03 21:10           ` Sasha Levin
2019-06-03 21:15             ` Jiri Kosina
2019-06-03 21:23               ` Linus Torvalds
2019-06-03 21:28                 ` Jiri Kosina
2019-06-03 22:11             ` Mark Brown
2019-06-04 17:16               ` Shuah Khan
2019-06-05  9:27                 ` Mark Brown
2019-06-05 11:48                   ` Geert Uytterhoeven
2019-06-05 18:16                     ` Shuah Khan
2019-06-05 13:19                 ` Sasha Levin
2019-06-05 19:05                   ` Shuah Khan
2019-06-04 18:09             ` Laura Abbott
2019-06-05 12:49               ` Sasha Levin
2019-06-04 21:43           ` Konstantin Ryabitsev
2019-06-04 22:02             ` Shuah Khan
2019-06-04 22:22               ` Konstantin Ryabitsev
2019-06-05 17:54                 ` Shuah Khan
2019-06-03 20:59       ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2019-05-29 22:34 Shuah Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1018c8ba-61a0-c024-cd98-3b82ebd710ec@redhat.com \
    --to=labbott@redhat.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox