[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1574247349.14298.30.camel@suse.com>
Date: Wed, 20 Nov 2019 11:55:49 +0100
From: Oliver Neukum <oneukum@...e.com>
To: Stephen Boyd <swboyd@...omium.org>, alexandre.belloni@...tlin.com,
andreyknvl@...gle.com, arnd@...db.de, b.zolnierkie@...sung.com,
gregkh@...uxfoundation.org, herbert@...dor.apana.org.au,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, lvivier@...hat.com,
mchehab+samsung@...nel.org, mpm@...enic.com,
syzbot <syzbot+f41c4f7c6d8b0b778780@...kaller.appspotmail.com>,
syzkaller-bugs@...glegroups.com
Subject: Re: INFO: task hung in chaoskey_disconnect
Am Freitag, den 15.11.2019, 09:51 -0800 schrieb Stephen Boyd:
> Quoting syzbot (2019-11-06 04:32:09)
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: b1aa9d83 usb: raw: add raw-gadget interface
> > git tree: https://github.com/google/kasan.git usb-fuzzer
> > console output: https://syzkaller.appspot.com/x/log.txt?x=16ae2adce00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=79de80330003b5f7
> > dashboard link: https://syzkaller.appspot.com/bug?extid=f41c4f7c6d8b0b778780
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10248158e00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16afbf7ce00000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+f41c4f7c6d8b0b778780@...kaller.appspotmail.com
>
> I suspect this is because of the kthread getting stuck problem reported
> by Maciej. Maybe try the commit that Herbert picked up.
Do you have a commit ID so we can test an exported patch?
Regards
Oliver
Powered by blists - more mailing lists