From: syzbot <syzbot+a39b5d3c50e55e24fb4d@syzkaller.appspotmail.com>
To: alsa-devel-owner@alsa-project.org, alsa-devel@alsa-project.org,
dan.carpenter@oracle.com, gustavo@embeddedor.com,
joe@perches.com, linux-kernel@vger.kernel.org, perex@perex.cz,
syzkaller-bugs@googlegroups.com, tiwai@suse.com, tiwai@suse.de,
vkoul@kernel.org
Subject: Re: KASAN: slab-out-of-bounds Read in linear_transfer
Date: Sun, 17 Mar 2019 03:43:01 -0700 [thread overview]
Message-ID: <0000000000009e4ca4058447ef02@google.com> (raw)
In-Reply-To: <00000000000052a5500584348100@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=11b70c2b200000
start commit: 65766ee0 ALSA: oss: Use kvzalloc() for local buffer alloca..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=13b70c2b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=15b70c2b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e1aaa1cfbfe1abf
dashboard link: https://syzkaller.appspot.com/bug?extid=a39b5d3c50e55e24fb4d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113945fb200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ed3cf7200000
Reported-by: syzbot+a39b5d3c50e55e24fb4d@syzkaller.appspotmail.com
Fixes: 65766ee0 ("ALSA: oss: Use kvzalloc() for local buffer allocations")
prev parent reply other threads:[~2019-03-17 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 11:32 KASAN: slab-out-of-bounds Read in linear_transfer syzbot
2019-03-16 11:52 ` syzbot
2019-03-17 10:43 ` 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=0000000000009e4ca4058447ef02@google.com \
--to=syzbot+a39b5d3c50e55e24fb4d@syzkaller.appspotmail.com \
--cc=alsa-devel-owner@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=gustavo@embeddedor.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).