From: Oliver Neukum <oneukum@suse.com>
To: Andrey Konovalov <andreyknvl@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: Mon, 19 Aug 2019 15:09:24 +0200 [thread overview]
Message-ID: <1566220164.5663.25.camel@suse.com> (raw)
In-Reply-To: <CAAeHK+xX3vk_JoJ=2tHF__LECxNmPXuPMkxWz6u+K6L-MdN=9g@mail.gmail.com>
Am Montag, den 19.08.2019, 14:43 +0200 schrieb Andrey Konovalov:
> On Mon, Aug 19, 2019 at 2:37 PM Oliver Neukum <oneukum@suse.com> wrote:
> > The original error was a divide by zero. The first fix fixed that
> > but still another error showed up. If I propose a fix there are
> > other possibilities besides it working.
> >
> > I could have no effect on the original bug or my fix breaks
> > something else and KASAN is making no difference between
> > those cases.
>
> I think you mean syzbot here and not KASAN. Do I understand correctly,
> that you're saying that the original report was
Yes, sorry syzbot.
> divide-by-zero, but
> when you requested to test the patch the reproducer triggered a
> use-after-free, and syzbot didn't treat the patch you provided as a
> correct fix?
No, obviously there is still a bug. What I would like syzbot to have
would be a third category: inconclusive.
Seeing another bug instead may also mean the first bug struck
before the second could ever happen. We just lack data to tell.
Regards
Oliver
next prev parent reply other threads:[~2019-08-19 13:09 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 [this message]
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
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=1566220164.5663.25.camel@suse.com \
--to=oneukum@suse.com \
--cc=andreyknvl@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.