From: Jiri Kosina <jikos@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Mon, 3 Jun 2019 23:15:17 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1906032311500.27227@cbobk.fhfr.pm> (raw)
In-Reply-To: <20190603211004.GU12898@sasha-vm>
On Mon, 3 Jun 2019, Sasha Levin wrote:
> > Apparently syzbot doesn't do well on the (a) side though. Honestly,
> > any system that just keeps things open for 300+ days has something
> > wrong with it. At some point it needs to be automatically either
> > closed, or re-notified. The "just keep it around" is simply not an
> > option.
>
> My understanding is that syzbot closes a bug once the bot sees an
> annotated commit indicating that it fixes a certain bug. These
> annotations get lost/forgotten/etc so bugs remain open even after they
> were fixed.
A lot of such bugs get fixed (directly or totally indirectly) without
authors of the fixes being even remotely aware of the syzbot report.
So being able to perform "ok, this is not an issue any more for whatever
reason, I am closing myself as RESOLVED" operation would be really nice to
have feature, which I think is currently missing.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-06-03 21:15 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
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 [this message]
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=nycvar.YFH.7.76.1906032311500.27227@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=sashal@kernel.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