From: syzbot <syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andreyknvl@google.com,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, elver@google.com,
glider@google.com, hotforest@gmail.com, houtao1@huawei.com,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: [syzbot] KASAN: vmalloc-out-of-bounds Write in ringbuf_map_alloc
Date: Wed, 02 Feb 2022 06:36:09 -0800 [thread overview]
Message-ID: <0000000000004cc7f905d709f0f6@google.com> (raw)
In-Reply-To: <0000000000000a9b7d05d6ee565f@google.com>
syzbot has bisected this issue to:
commit c34cdf846c1298de1c0f7fbe04820fe96c45068c
Author: Andrey Konovalov <andreyknvl@google.com>
Date: Wed Feb 2 01:04:27 2022 +0000
kasan, vmalloc: unpoison VM_ALLOC pages after mapping
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128cb900700000
start commit: 6abab1b81b65 Add linux-next specific files for 20220202
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=118cb900700000
console output: https://syzkaller.appspot.com/x/log.txt?x=168cb900700000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8d8750556896349
dashboard link: https://syzkaller.appspot.com/bug?extid=5ad567a418794b9b5983
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1450d9f0700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130ef35bb00000
Reported-by: syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com
Fixes: c34cdf846c12 ("kasan, vmalloc: unpoison VM_ALLOC pages after mapping")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-02 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 5:40 [syzbot] KASAN: vmalloc-out-of-bounds Write in ringbuf_map_alloc syzbot
2022-02-02 12:11 ` syzbot
2022-02-02 12:20 ` Daniel Borkmann
2022-02-02 14:49 ` syzbot
2022-02-02 14:36 ` syzbot [this message]
2022-02-02 14:49 ` Marco Elver
2022-02-02 14:55 ` Daniel Borkmann
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=0000000000004cc7f905d709f0f6@google.com \
--to=syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hotforest@gmail.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--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.