From: syzbot <syzbot+3acd9f67a6a15766686e@syzkaller.appspotmail.com>
To: ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, john.fastabend@gmail.com, kafai@fb.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, yhs@fb.com
Subject: Re: KASAN: use-after-free Read in sk_psock_unlink
Date: Wed, 22 May 2019 14:49:00 -0700 [thread overview]
Message-ID: <000000000000e7e3a5058980ee7b@google.com> (raw)
In-Reply-To: <000000000000fd342e05791cc86f@google.com>
syzbot has bisected this bug to:
commit 48a3c64b4649b5b23a4ca756af93b4ee820ff883
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri Jun 29 14:11:03 2018 +0000
Merge tag 'drm-fixes-2018-06-29' of
git://anongit.freedesktop.org/drm/drm
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11f92d6ca00000
start commit: f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=13f92d6ca00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15f92d6ca00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc045131472947d7
dashboard link: https://syzkaller.appspot.com/bug?extid=3acd9f67a6a15766686e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13adf56ca00000
Reported-by: syzbot+3acd9f67a6a15766686e@syzkaller.appspotmail.com
Fixes: 48a3c64b4649 ("Merge tag 'drm-fixes-2018-06-29' of
git://anongit.freedesktop.org/drm/drm")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-05-22 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:37 KASAN: use-after-free Read in sk_psock_unlink syzbot
2019-05-22 14:45 ` syzbot
2019-05-22 21:49 ` syzbot [this message]
2019-05-22 22:58 ` Linus Torvalds
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=000000000000e7e3a5058980ee7b@google.com \
--to=syzbot+3acd9f67a6a15766686e@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--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.