From: syzbot <syzbot+4476917c053f60112c99@syzkaller.appspotmail.com>
To: alexandre.belloni@bootlin.com, allison@lohutok.net,
alsa-devel-owner@alsa-project.org, alsa-devel@alsa-project.org,
bhelgaas@google.com, enric.balletbo@collabora.com,
gregkh@linuxfoundation.org, kirr@nexedi.com,
linux-kernel@vger.kernel.org, lkundrak@v3.sk,
logang@deltatee.com, perex@perex.cz, rfontana@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tiwai@suse.com, tiwai@suse.de
Subject: Re: KASAN: use-after-free Read in snd_timer_open
Date: Mon, 11 Nov 2019 15:45:01 -0800 [thread overview]
Message-ID: <00000000000058443705971ab84d@google.com> (raw)
In-Reply-To: <0000000000007f69a2059714b34d@google.com>
syzbot has bisected this bug to:
commit 6a34367e52caea1413eb0a0dcbb524f0c9b67e82
Author: Takashi Iwai <tiwai@suse.de>
Date: Thu Nov 7 19:20:08 2019 +0000
ALSA: timer: Fix possible race at assigning a timer instance
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16b5dde6e00000
start commit: 6980b7f6 Add linux-next specific files for 20191111
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=15b5dde6e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11b5dde6e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2af7db1972ec750e
dashboard link: https://syzkaller.appspot.com/bug?extid=4476917c053f60112c99
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108fbfece00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1055d5aae00000
Reported-by: syzbot+4476917c053f60112c99@syzkaller.appspotmail.com
Fixes: 6a34367e52ca ("ALSA: timer: Fix possible race at assigning a timer
instance")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-11 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 16:34 KASAN: use-after-free Read in snd_timer_open syzbot
2019-11-11 23:45 ` syzbot [this message]
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=00000000000058443705971ab84d@google.com \
--to=syzbot+4476917c053f60112c99@syzkaller.appspotmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allison@lohutok.net \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=bhelgaas@google.com \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kirr@nexedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=logang@deltatee.com \
--cc=perex@perex.cz \
--cc=rfontana@redhat.com \
--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