Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <5dd59f4f.1c69fb81.17c48.0540@mx.google.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1574247349.14298.30.camel@suse.com>
References: <000000000000cdaa560596acbc4e@google.com> <5dcee59a.1c69fb81.188d.e4b9@mx.google.com> <1574247349.14298.30.camel@suse.com>
Subject: Re: INFO: task hung in chaoskey_disconnect
From:   Stephen Boyd <swboyd@chromium.org>
To:     Oliver Neukum <oneukum@suse.com>, alexandre.belloni@bootlin.com,
        andreyknvl@google.com, arnd@arndb.de, b.zolnierkie@samsung.com,
        gregkh@linuxfoundation.org, herbert@gondor.apana.org.au,
        linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-usb@vger.kernel.org, lvivier@redhat.com,
        mchehab+samsung@kernel.org, mpm@selenic.com,
        syzbot <syzbot+f41c4f7c6d8b0b778780@syzkaller.appspotmail.com>,
        syzkaller-bugs@googlegroups.com
User-Agent: alot/0.8.1
Date:   Wed, 20 Nov 2019 12:17:18 -0800
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Quoting Oliver Neukum (2019-11-20 02:55:49)
> Am Freitag, den 15.11.2019, 09:51 -0800 schrieb Stephen Boyd:
> > Quoting syzbot (2019-11-06 04:32:09)
> > > Hello,
> > >=20
> > > syzbot found the following crash on:
> > >=20
> > > 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=3D16ae2adce=
00000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=3D79de80330=
003b5f7
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=3Df41c4f7c6d8=
b0b778780
> > > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=3D1024815=
8e00000
> > > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=3D16afbf7ce=
00000
> > >=20
> > > IMPORTANT: if you fix the bug, please add the following tag to the co=
mmit:
> > > Reported-by: syzbot+f41c4f7c6d8b0b778780@syzkaller.appspotmail.com
> >=20
> > I suspect this is because of the kthread getting stuck problem reported
> > by Maciej. Maybe try the commit that Herbert picked up.
>=20
> Do you have a commit ID so we can test an exported patch?
>=20

I sent the patch in. See https://lkml.kernel.org/r/00000000000019acd8059770=
942b@google.com
for what happened. It didn't make a difference. I'll have to stare at it
a little more to figure out what's going on.