From: syzbot <syzbot+9a901acbc447313bfe3e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ast@kernel.org, cai@lca.pw,
crecklin@redhat.com, daniel@iogearbox.net, dvyukov@google.com,
john.fastabend@gmail.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in corrupted (2)
Date: Thu, 06 Jun 2019 14:26:00 -0700 [thread overview]
Message-ID: <0000000000004c11d6058aae5c30@google.com> (raw)
In-Reply-To: <0000000000004945f1058aa80556@google.com>
syzbot has bisected this bug to:
commit d40b0116c94bd8fc2b63aae35ce8e66bb53bba42
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu Aug 16 19:49:08 2018 +0000
bpf, sockmap: fix leakage of smap_psock_map_entry
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1137e90ea00000
start commit: 156c0591 Merge tag 'linux-kselftest-5.2-rc4' of git://git...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1337e90ea00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1537e90ea00000
kernel config: https://syzkaller.appspot.com/x/.config?x=60564cb52ab29d5b
dashboard link: https://syzkaller.appspot.com/bug?extid=9a901acbc447313bfe3e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a4b01ea00000
Reported-by: syzbot+9a901acbc447313bfe3e@syzkaller.appspotmail.com
Fixes: d40b0116c94b ("bpf, sockmap: fix leakage of smap_psock_map_entry")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-06-06 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 13:52 KASAN: slab-out-of-bounds Read in corrupted (2) syzbot
2019-06-06 14:41 ` Dmitry Vyukov
2019-06-06 21:26 ` 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=0000000000004c11d6058aae5c30@google.com \
--to=syzbot+9a901acbc447313bfe3e@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=cai@lca.pw \
--cc=crecklin@redhat.com \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=john.fastabend@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.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.