From: syzbot <syzbot+561a74f84100162990b2@syzkaller.appspotmail.com>
To: alsa-devel-owner@alsa-project.org, alsa-devel@alsa-project.org,
arnd@arndb.de, baolin.wang@linaro.org, boqun.feng@gmail.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
paulhsia@chromium.org, perex@perex.cz, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tiwai@suse.com, tiwai@suse.de,
will@kernel.org
Subject: Re: possible deadlock in _snd_pcm_stream_lock_irqsave
Date: Wed, 09 Sep 2020 10:33:04 -0700 [thread overview]
Message-ID: <00000000000017994005aee4d82d@google.com> (raw)
In-Reply-To: <0000000000002cc32605aedd876d@google.com>
syzbot has bisected this issue to:
commit e918188611f073063415f40fae568fa4d86d9044
Author: Boqun Feng <boqun.feng@gmail.com>
Date: Fri Aug 7 07:42:20 2020 +0000
locking: More accurate annotations for read_lock()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=112dc243900000
start commit: dff9f829 Add linux-next specific files for 20200908
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=132dc243900000
console output: https://syzkaller.appspot.com/x/log.txt?x=152dc243900000
kernel config: https://syzkaller.appspot.com/x/.config?x=37b3426c77bda44c
dashboard link: https://syzkaller.appspot.com/bug?extid=561a74f84100162990b2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1209e245900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154b15ed900000
Reported-by: syzbot+561a74f84100162990b2@syzkaller.appspotmail.com
Fixes: e918188611f0 ("locking: More accurate annotations for read_lock()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-09 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:49 possible deadlock in _snd_pcm_stream_lock_irqsave syzbot
2020-09-09 17:33 ` syzbot [this message]
2020-09-10 4:50 ` Boqun Feng
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=00000000000017994005aee4d82d@google.com \
--to=syzbot+561a74f84100162990b2@syzkaller.appspotmail.com \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulhsia@chromium.org \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=will@kernel.org \
/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