From: syzbot <syzbot+29093015c21333d1c46d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bunk@kernel.org, ebiggers@google.com,
gregkh@linuxfoundation.org, jannh@google.com,
jrdr.linux@gmail.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux@dominikbrodowski.net,
mawilcox@microsoft.com, mojha@codeaurora.org,
rientjes@google.com, sudipm.mukherjee@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuehaibing@huawei.com
Subject: Re: KASAN: use-after-free Read in relay_switch_subbuf
Date: Sun, 17 Nov 2019 22:59:00 -0800 [thread overview]
Message-ID: <000000000000795dd20597997b1c@google.com> (raw)
In-Reply-To: <0000000000002e4a260576c1589d@google.com>
syzbot has bisected this bug to:
commit 21c75ad65f8e5213ec542d99c259ffe3e3671e81
Author: YueHaibing <yuehaibing@huawei.com>
Date: Thu Mar 21 08:26:28 2019 +0000
parport_cs: Fix memory leak in parport_config
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11480c6ae00000
start commit: 26bc6721 Merge tag 'for-linus-2019-11-05' of git://git.ker..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=13480c6ae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15480c6ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5e2eca3f31f9bf
dashboard link: https://syzkaller.appspot.com/bug?extid=29093015c21333d1c46d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132afbcce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=179a1f8ae00000
Reported-by: syzbot+29093015c21333d1c46d@syzkaller.appspotmail.com
Fixes: 21c75ad65f8e ("parport_cs: Fix memory leak in parport_config")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-18 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 7:41 KASAN: use-after-free Read in relay_switch_subbuf syzbot
2019-11-06 7:58 ` syzbot
2019-11-18 6:59 ` 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=000000000000795dd20597997b1c@google.com \
--to=syzbot+29093015c21333d1c46d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=jrdr.linux@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mawilcox@microsoft.com \
--cc=mojha@codeaurora.org \
--cc=rientjes@google.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuehaibing@huawei.com \
/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