From: syzbot <syzbot+f1048ebddb93befb085f@syzkaller.appspotmail.com>
To: alexandre.belloni@bootlin.com, alsa-devel-owner@alsa-project.org,
alsa-devel@alsa-project.org, bhelgaas@google.com,
broonie@kernel.org, kirr@nexedi.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net, lkundrak@v3.sk,
maxime.ripard@bootlin.com, perex@perex.cz, peron.clem@gmail.com,
robh@kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tiwai@suse.com, tiwai@suse.de
Subject: Re: INFO: task hung in snd_timer_close
Date: Wed, 06 Nov 2019 04:05:00 -0800 [thread overview]
Message-ID: <000000000000b9dd9c0596ac5b94@google.com> (raw)
In-Reply-To: <0000000000004dfaf005969d1755@google.com>
syzbot has bisected this bug to:
commit b2045303147254d01b1db90a83e5df3832c4264b
Author: Clément Péron <peron.clem@gmail.com>
Date: Mon May 27 20:06:21 2019 +0000
dt-bindings: sound: sun4i-spdif: Add Allwinner H6 compatible
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14acecb4e00000
start commit: a99d8080 Linux 5.4-rc6
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=16acecb4e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12acecb4e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5e2eca3f31f9bf
dashboard link: https://syzkaller.appspot.com/bug?extid=f1048ebddb93befb085f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126bc658e00000
Reported-by: syzbot+f1048ebddb93befb085f@syzkaller.appspotmail.com
Fixes: b20453031472 ("dt-bindings: sound: sun4i-spdif: Add Allwinner H6
compatible")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-06 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 17:52 INFO: task hung in snd_timer_close syzbot
2019-11-06 12:05 ` syzbot [this message]
2019-11-06 12:13 ` Mark Brown
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=000000000000b9dd9c0596ac5b94@google.com \
--to=syzbot+f1048ebddb93befb085f@syzkaller.appspotmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=kirr@nexedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkundrak@v3.sk \
--cc=maxime.ripard@bootlin.com \
--cc=perex@perex.cz \
--cc=peron.clem@gmail.com \
--cc=robh@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox