Am Donnerstag, den 09.03.2017, 06:42 +0100 schrieb Greg KH:
> On Mon, Feb 20, 2017 at 03:38:42PM +0100, Oliver Neukum wrote:
> >
> > There is a small window during which the an URB may
> > remain active after disconnect has returned. If in that case
> > already freed memory may be accessed and exe
On Mon, Feb 20, 2017 at 03:38:42PM +0100, Oliver Neukum wrote:
> There is a small window during which the an URB may
> remain active after disconnect has returned. If in that case
> already freed memory may be accessed and executed.
>
> The fix is to poison the URB befotre the work is flushed.
>
Am Montag, den 20.02.2017, 19:51 +0300 schrieb Sergei Shtylyov:
> On 02/20/2017 05:38 PM, Oliver Neukum wrote:
>
> >
> > There is a small window during which the an URB may
>
> So the or an?
That is a question of view point which I cannot give an objective
answer to. There is one URB per de
On 02/20/2017 05:38 PM, Oliver Neukum wrote:
There is a small window during which the an URB may
So the or an?
remain active after disconnect has returned. If in that case
already freed memory may be accessed and executed.
The fix is to poison the URB befotre the work is flushed.
Signed
There is a small window during which the an URB may
remain active after disconnect has returned. If in that case
already freed memory may be accessed and executed.
The fix is to poison the URB befotre the work is flushed.
Signed-off-by: Oliver Neukum
---
drivers/usb/misc/lvstest.c | 2 ++
1 fil
