All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Mon, 3 Jun 2019 14:23:47 -0700	[thread overview]
Message-ID: <CAHk-=wh1sN4v3a=jfucUYvwdFQUc7ASiYrrbzXzZ3YMerN=7oQ@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1906032311500.27227@cbobk.fhfr.pm>

On Mon, Jun 3, 2019 at 2:15 PM Jiri Kosina <jikos@kernel.org> wrote:
>
> 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.

Honestly, syzbot - or some related infrastructure - should just do
that automatically.

If the syzbot bug is old, and no longer reproduces with modern
kernels, then just close it. No human should waste any time on that.

As you say, syzbot can find things that others find independently, so
it's not even a "syzbot didn't get the credit, and didn't close things
as a result" issue. It can just as well be "bug was fixed without
syzbot being directly involved at all, and the syzbot report is just
stale old data".

                     Linus

  reply	other threads:[~2019-06-03 21:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 23:30 [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs! 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
2019-06-03 21:23               ` Linus Torvalds [this message]
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='CAHk-=wh1sN4v3a=jfucUYvwdFQUc7ASiYrrbzXzZ3YMerN=7oQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=jikos@kernel.org \
    --cc=ksummit-discuss@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.