Re: [PATCH 4.19 108/125] USB: yurex: Fix bad gfp argument

2020-09-02 Thread Alan Stern
On Wed, Sep 02, 2020 at 02:58:27PM +0200, Pavel Machek wrote: > Hi! > > > The syzbot fuzzer identified a bug in the yurex driver: It passes > > GFP_KERNEL as a memory-allocation flag to usb_submit_urb() at a time > > when its state is TASK_INTERRUPTIBLE, not TASK_RUNNING: > > Yeah, and instead

Re: [PATCH 4.19 108/125] USB: yurex: Fix bad gfp argument

2020-09-02 Thread Greg Kroah-Hartman
On Wed, Sep 02, 2020 at 02:58:27PM +0200, Pavel Machek wrote: > Hi! > > > The syzbot fuzzer identified a bug in the yurex driver: It passes > > GFP_KERNEL as a memory-allocation flag to usb_submit_urb() at a time > > when its state is TASK_INTERRUPTIBLE, not TASK_RUNNING: > > Yeah, and instead

Re: [PATCH 4.19 108/125] USB: yurex: Fix bad gfp argument

2020-09-02 Thread Pavel Machek
Hi! > The syzbot fuzzer identified a bug in the yurex driver: It passes > GFP_KERNEL as a memory-allocation flag to usb_submit_urb() at a time > when its state is TASK_INTERRUPTIBLE, not TASK_RUNNING: Yeah, and instead of fixing the bug, patch papers over it, reducing reliability of the driver

[PATCH 4.19 108/125] USB: yurex: Fix bad gfp argument

2020-09-01 Thread Greg Kroah-Hartman
From: Alan Stern commit f176ede3a3bde5b398a6777a7f9ff091baa2d3ff upstream. The syzbot fuzzer identified a bug in the yurex driver: It passes GFP_KERNEL as a memory-allocation flag to usb_submit_urb() at a time when its state is TASK_INTERRUPTIBLE, not TASK_RUNNING: do not call blocking ops