From: Stephen Boyd <swboyd@chromium.org>
To: 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
Subject: Re: INFO: task hung in chaoskey_disconnect
Date: Fri, 15 Nov 2019 09:51:21 -0800 [thread overview]
Message-ID: <5dcee59a.1c69fb81.188d.e4b9@mx.google.com> (raw)
In-Reply-To: <000000000000cdaa560596acbc4e@google.com>
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@syzkaller.appspotmail.com
I suspect this is because of the kthread getting stuck problem reported
by Maciej. Maybe try the commit that Herbert picked up.
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
next prev parent reply other threads:[~2019-11-15 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:32 INFO: task hung in chaoskey_disconnect syzbot
2019-11-15 17:51 ` Stephen Boyd [this message]
2019-11-15 17:51 ` syzbot
2019-11-20 10:55 ` Oliver Neukum
2019-11-20 20:17 ` Stephen Boyd
2019-11-15 18:47 ` Stephen Boyd
2019-11-16 6:11 ` syzbot
2020-06-18 12:13 ` Andrey Konovalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dcee59a.1c69fb81.188d.e4b9@mx.google.com \
--to=swboyd@chromium.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=mchehab+samsung@kernel.org \
--cc=mpm@selenic.com \
--cc=syzbot+f41c4f7c6d8b0b778780@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.