From: syzbot <syzbot+12f17c177de05efea72d@syzkaller.appspotmail.com>
To: alsa-devel-bounces@alsa-project.org, alsa-devel@alsa-project.org,
dan.carpenter@oracle.com, gustavo@embeddedor.com,
joe@perches.com, liam.r.girdwood@linux.intel.com,
linux-kernel@vger.kernel.org, o-takashi@sakamocchi.jp,
pasqualirb@gmail.com, perex@perex.cz,
syzkaller-bugs@googlegroups.com, tiwai@suse.com, tiwai@suse.de,
twischer@de.adit-jv.com, vkoul@kernel.org
Subject: Re: KASAN: slab-out-of-bounds Write in default_read_copy_kernel
Date: Sat, 16 Mar 2019 07:49:02 -0700 [thread overview]
Message-ID: <00000000000097b4a405843741e6@google.com> (raw)
In-Reply-To: <0000000000004a6256057ca3b6bd@google.com>
syzbot has bisected this bug to:
commit 65766ee0bf7fe8b3be80e2e1c3ef54ad59b29476
Author: Takashi Iwai <tiwai@suse.de>
Date: Fri Nov 9 10:59:45 2018 +0000
ALSA: oss: Use kvzalloc() for local buffer allocations
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ae57db200000
start commit: 65766ee0 ALSA: oss: Use kvzalloc() for local buffer alloca..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=106e57db200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17ae57db200000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9cc5a440391cbfd
dashboard link: https://syzkaller.appspot.com/bug?extid=12f17c177de05efea72d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c27125400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=152a2a43400000
Reported-by: syzbot+12f17c177de05efea72d@syzkaller.appspotmail.com
Fixes: 65766ee0 ("ALSA: oss: Use kvzalloc() for local buffer allocations")
next prev parent reply other threads:[~2019-03-16 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 4:51 KASAN: slab-out-of-bounds Write in default_read_copy_kernel syzbot
2019-03-16 14:49 ` syzbot [this message]
2019-03-19 13:35 ` Takashi Iwai
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=00000000000097b4a405843741e6@google.com \
--to=syzbot+12f17c177de05efea72d@syzkaller.appspotmail.com \
--cc=alsa-devel-bounces@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=gustavo@embeddedor.com \
--cc=joe@perches.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=pasqualirb@gmail.com \
--cc=perex@perex.cz \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=twischer@de.adit-jv.com \
--cc=vkoul@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