From: syzbot <syzbot+59b7daa4315e07a994f1@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andriin@fb.com,
aryabinin@virtuozzo.com, ast@kernel.org, bpf@vger.kernel.org,
christophe.leroy@c-s.fr, daniel@iogearbox.net, dja@axtens.net,
dvyukov@google.com, glider@google.com, gor@linux.ibm.com,
kafai@fb.com, linux-kernel@vger.kernel.org, mark.rutland@arm.com,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
yhs@fb.com
Subject: Re: KASAN: vmalloc-out-of-bounds Write in pcpu_alloc
Date: Wed, 04 Dec 2019 17:55:00 -0800 [thread overview]
Message-ID: <000000000000918b470598eb37b7@google.com> (raw)
In-Reply-To: <0000000000008399d40598d8a34d@google.com>
syzbot has bisected this bug to:
commit 0609ae011deb41c9629b7f5fd626dfa1ac9d16b0
Author: Daniel Axtens <dja@axtens.net>
Date: Sun Dec 1 01:55:00 2019 +0000
x86/kasan: support KASAN_VMALLOC
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10c70f36e00000
start commit: b3c424eb sch_cake: Add missing NLA policy entry TCA_CAKE_S..
git tree: bpf
final crash: https://syzkaller.appspot.com/x/report.txt?x=12c70f36e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14c70f36e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d8ab2e0e09c2a82
dashboard link: https://syzkaller.appspot.com/bug?extid=59b7daa4315e07a994f1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=140df641e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147dcc2ae00000
Reported-by: syzbot+59b7daa4315e07a994f1@syzkaller.appspotmail.com
Fixes: 0609ae011deb ("x86/kasan: support KASAN_VMALLOC")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-05 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 3:45 KASAN: vmalloc-out-of-bounds Write in pcpu_alloc syzbot
2019-12-05 1:55 ` 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=000000000000918b470598eb37b7@google.com \
--to=syzbot+59b7daa4315e07a994f1@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriin@fb.com \
--cc=aryabinin@virtuozzo.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christophe.leroy@c-s.fr \
--cc=daniel@iogearbox.net \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.