All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: syzbot <syzbot+55b0304b360654a7537b@syzkaller.appspotmail.com>,
	andreyknvl@google.com, syzkaller-bugs@googlegroups.com,
	steve_bayless@keysight.com, gregkh@linuxfoundation.org,
	guido.kiener@rohde-schwarz.com, linux-usb@vger.kernel.org
Subject: Re: divide error in usbtmc_generic_read
Date: Thu, 15 Aug 2019 15:31:26 +0200	[thread overview]
Message-ID: <1565875886.5780.7.camel@suse.com> (raw)
In-Reply-To: <000000000000a59094059013dd63@google.com>

Am Mittwoch, den 14.08.2019, 06:38 -0700 schrieb syzbot:
> syzbot has tested the proposed patch but the reproducer still triggered  
> crash:
> KASAN: use-after-free Read in usbtmc_disconnect

I am afraid that is a difficiency in KASAN that should be fixed.
Is the class of the error compared if I leave in more of the
original bug report? Actually the ID is still there, so it really
should return an inconclusive in these cases.

	Regards
		Oliver


  parent reply	other threads:[~2019-08-15 13:31 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 [this message]
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
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=1565875886.5780.7.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.