From: butt3rflyh4ck <butterflyhuangxx@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: A slab-out-of-bounds Read bug in __htab_map_lookup_and_delete_batch
Date: Thu, 6 Jan 2022 14:02:36 +0800 [thread overview]
Message-ID: <CAFcO6XP6+=S1C_m28JF_aA5az=WiswS-J3d8X2dBsYyQ4nwzkg@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQ+HJnZOqGjXKXut51BUqi=+na4cj=PFaE35u9QwZDgeVQ@mail.gmail.com>
> >
> > Hi, the attachment is a reproducer. Enjoy it.
>
> Please do not top-post.
> Forwarding a syzbot reproducer with zero effort to analyze
> what's going on is kinda lame.
Hi, I am sorry for that.
> Maybe try harder and come up with a fix?
> Or at least try git bisect and based on a commit find and
> cc an author so it can be fixed (assuming issue still exists
> in bpf-next) ?
>
Thank you for your suggestions.
I spent a few days on git bisect and locked the bad commit, the commit
is d635a69dd4981cc51f90293f5f64268620ed1565.
The commit is a Merge tag 'net-next-5.11' and Contains multiple
commits, currently not locked to a single commit.
Regards,
but3rflyh4ck.
--
Active Defense Lab of Venustech
next prev parent reply other threads:[~2022-01-06 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 10:10 A slab-out-of-bounds Read bug in __htab_map_lookup_and_delete_batch butt3rflyh4ck
2021-12-30 2:23 ` Alexei Starovoitov
2021-12-30 3:23 ` butt3rflyh4ck
2021-12-30 4:00 ` Alexei Starovoitov
2022-01-06 6:02 ` butt3rflyh4ck [this message]
2022-01-07 1:19 ` Yonghong Song
2022-01-07 3:25 ` butt3rflyh4ck
2022-01-07 4:02 ` Yonghong Song
2022-01-07 5:42 ` butt3rflyh4ck
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='CAFcO6XP6+=S1C_m28JF_aA5az=WiswS-J3d8X2dBsYyQ4nwzkg@mail.gmail.com' \
--to=butterflyhuangxx@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).