Re: divide error in usbtmc_generic_read

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Montag, den 19.08.2019, 14:17 +0200 schrieb Andrey Konovalov:
> On Thu, Aug 15, 2019 at 3:31 PM Oliver Neukum <oneukum@xxxxxxxx> wrote:
> > 
> > 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.
> 
> I don't get this, what kind of deficiency do you mean?

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.

	Regards
		Oliver




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux