From: Oliver Neukum <oneukum@suse.com>
To: Andrey Konovalov <andreyknvl@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Cc: syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
steve_bayless@keysight.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
guido.kiener@rohde-schwarz.com,
syzbot <syzbot+55b0304b360654a7537b@syzkaller.appspotmail.com>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: divide error in usbtmc_generic_read
Date: Tue, 20 Aug 2019 11:01:29 +0200 [thread overview]
Message-ID: <1566291689.11678.3.camel@suse.com> (raw)
In-Reply-To: <CAAeHK+xum44QNGCgnFc-W69AfA4Rt1hEiRc4SrSWhFfqhhuf0A@mail.gmail.com>
Am Montag, den 19.08.2019, 17:40 +0200 schrieb Andrey Konovalov:
>
> This implies that we can differentiate between different crashes. We
> can differentiate between different manifestations of crashes, but
> those can be caused by the same bug. I think we can remove the word
> "still" though, so the words will be: "syzbot has tested the proposed
> patch, but the reproducer triggered a crash".
That is exactly my point. There are three cases:
- no crash
- clearly the same crash
- something
Yet syzbot has two answers only. We are killing information needlessly.
Regards
Oliver
next prev parent reply other threads:[~2019-08-20 9:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 11:38 divide error in usbtmc_generic_read syzbot
2019-08-14 13:25 ` Oliver Neukum
2019-08-14 13:38 ` syzbot
2019-08-14 13:52 ` Andrey Konovalov
2019-08-15 13:31 ` Oliver Neukum
2019-08-19 12:17 ` Andrey Konovalov
2019-08-19 12:37 ` Oliver Neukum
2019-08-19 12:43 ` Andrey Konovalov
2019-08-19 13:09 ` Oliver Neukum
2019-08-19 13:18 ` Andrey Konovalov
2019-08-19 13:49 ` Oliver Neukum
2019-08-19 15:40 ` Andrey Konovalov
2019-08-20 9:01 ` Oliver Neukum [this message]
2019-08-15 14:28 ` Oliver Neukum
2019-08-15 14:48 ` syzbot
2019-11-19 13:35 ` Andrey Konovalov
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=1566291689.11678.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=guido.kiener@rohde-schwarz.com \
--cc=linux-usb@vger.kernel.org \
--cc=steve_bayless@keysight.com \
--cc=syzbot+55b0304b360654a7537b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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.