From: syzbot <syzbot+845923d2172947529b58@syzkaller•appspotmail.com>
To: andrii@kernel•org, andriin@fb•com, ast@kernel•org,
bpf@vger•kernel.org, coreteam@netfilter•org,
daniel@iogearbox•net, davem@davemloft•net, hawk@kernel•org,
john.fastabend@gmail•com, kaber@trash•net,
kadlec@blackhole•kfki.hu, kafai@fb•com, kpsingh@chromium•org,
kpsingh@kernel•org, kuba@kernel•org,
linux-kernel@vger•kernel.org, linux-media@vger•kernel.org,
mathieu.desnoyers@efficios•com, mchehab@kernel•org,
mchehab@s-opensource•com, mingo@kernel•org, mingo@redhat•com,
mmullins@mmlx•us, netdev@vger•kernel.org,
netfilter-devel@vger•kernel.org, pablo@netfilter•org,
peterz@infradead•org, rostedt@goodmis•org, songliubraving@fb•com,
syzkaller-bugs@googlegroups•com, yhs@fb•com
Subject: Re: [syzbot] KASAN: vmalloc-out-of-bounds Read in bpf_trace_run2
Date: Wed, 31 Mar 2021 20:39:05 -0700 [thread overview]
Message-ID: <0000000000002c193805bee0f97c@google.com> (raw)
In-Reply-To: <00000000000046e0e905afcff205@google.com>
syzbot suspects this issue was fixed by commit:
commit befe6d946551d65cddbd32b9cb0170b0249fd5ed
Author: Steven Rostedt (VMware) <rostedt@goodmis•org>
Date: Wed Nov 18 14:34:05 2020 +0000
tracepoint: Do not fail unregistering a probe due to memory failure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=123358a1d00000
start commit: 70b97111 bpf: Use hlist_add_head_rcu when linking to local..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=7e0ca96a9b6ee858
dashboard link: https://syzkaller.appspot.com/bug?extid=845923d2172947529b58
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10193f3b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168c729b900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: tracepoint: Do not fail unregistering a probe due to memory failure
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-04-01 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 10:02 KASAN: vmalloc-out-of-bounds Read in bpf_trace_run2 syzbot
2021-04-01 3:39 ` syzbot [this message]
2021-04-13 17:20 ` [syzbot] " Dmitry Vyukov
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=0000000000002c193805bee0f97c@google.com \
--to=syzbot+845923d2172947529b58@syzkaller$(echo .)appspotmail.com \
--cc=andrii@kernel$(echo .)org \
--cc=andriin@fb$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=coreteam@netfilter$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=hawk@kernel$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=kadlec@blackhole$(echo .)kfki.hu \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@chromium$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=mchehab@kernel$(echo .)org \
--cc=mchehab@s-opensource$(echo .)com \
--cc=mingo@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=mmullins@mmlx$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=songliubraving@fb$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox