Hi Brad,
On Tue, Aug 13, 2019 at 01:48:34PM -0500, Brad Love wrote:
> > On Mon, Aug 12, 2019 at 10:21:39AM -0300, Ezequiel Garcia wrote:
> >> On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
> >>> syzbot reports an error on flush_request_modules() for the second device.
> >>> This workqueue wa
Hey Sean,
On 13/08/2019 04.10, Sean Young wrote:
> Hi Brad,
>
> On Mon, Aug 12, 2019 at 10:21:39AM -0300, Ezequiel Garcia wrote:
>> On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
>>> syzbot reports an error on flush_request_modules() for the second device.
>>> This workqueue was never initi
Hi Brad,
On Mon, Aug 12, 2019 at 10:21:39AM -0300, Ezequiel Garcia wrote:
> On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
> > syzbot reports an error on flush_request_modules() for the second device.
> > This workqueue was never initialised so simply remove the offending line.
> >
> > usb
On Mon, Aug 12, 2019 at 10:21:39AM -0300, Ezequiel Garcia wrote:
> On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
> > syzbot reports an error on flush_request_modules() for the second device.
> > This workqueue was never initialised so simply remove the offending line.
> >
> > usb 1-1: USB d
On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
> syzbot reports an error on flush_request_modules() for the second device.
> This workqueue was never initialised so simply remove the offending line.
>
> usb 1-1: USB disconnect, device number 2
> em28xx 1-1:1.153: Disconnecting em28xx #1
> --
syzbot reports an error on flush_request_modules() for the second device.
This workqueue was never initialised so simply remove the offending line.
usb 1-1: USB disconnect, device number 2
em28xx 1-1:1.153: Disconnecting em28xx #1
[ cut here ]
WARNING: CPU: 0 PID: 12 at ker
