All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+10cffda23c81a3ff1088@syzkaller.appspotmail.com>
To: ast@fb.com, ast@kernel.org, daniel@iogearbox.net,
	john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in bpf_prog_kallsyms_del
Date: Wed, 27 Mar 2019 05:55:00 -0700	[thread overview]
Message-ID: <000000000000141efb058512f295@google.com> (raw)
In-Reply-To: <0000000000001d985405783e8aee@google.com>

syzbot has bisected this bug to:

commit f4d7e40a5b7157e1329c3c5b10f60d8289fc2941
Author: Alexei Starovoitov <ast@fb.com>
Date:   Fri Dec 15 01:55:06 2017 +0000

     bpf: introduce function calls (verification)

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14d1915d200000
start commit:   1ce80e0f Merge tag 'fsnotify_for_v4.20-rc3' of git://git.k..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=16d1915d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12d1915d200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
dashboard link: https://syzkaller.appspot.com/bug?extid=10cffda23c81a3ff1088
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17e0be2b400000

Reported-by: syzbot+10cffda23c81a3ff1088@syzkaller.appspotmail.com
Fixes: f4d7e40a5b71 ("bpf: introduce function calls (verification)")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2019-03-27 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  6:28 KASAN: use-after-free Read in bpf_prog_kallsyms_del syzbot
2018-11-18 18:14 ` syzbot
2019-03-27 12: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=000000000000141efb058512f295@google.com \
    --to=syzbot+10cffda23c81a3ff1088@syzkaller.appspotmail.com \
    --cc=ast@fb.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.