From: patchwork-bot+netdevbpf@kernel.org
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] libbpf: fix fuzzer-reported issues
Date: Thu, 13 Oct 2022 16:00:19 +0000 [thread overview]
Message-ID: <166567681973.4134.13920189690256469312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221012022353.7350-1-shung-hsi.yu@suse.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 12 Oct 2022 10:23:50 +0800 you wrote:
> Hi, this patch set fixes several fuzzer-reported issues of libbpf when
> dealing with (malformed) BPF object file:
>
> - patch #1 fix out-of-bound heap write reported by oss-fuzz (currently
> incorrectly marked as fixed)
>
> - patch #2 and #3 fix null-pointer dereference found by locally-run
> fuzzer.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] libbpf: use elf_getshdrnum() instead of e_shnum
https://git.kernel.org/bpf/bpf-next/c/ea306bb65ff8
- [bpf-next,v2,2/3] libbpf: deal with section with no data gracefully
https://git.kernel.org/bpf/bpf-next/c/662e24598d8c
- [bpf-next,v2,3/3] libbpf: fix null-pointer dereference in find_prog_by_sec_insn()
https://git.kernel.org/bpf/bpf-next/c/79d0ca2d19bf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-13 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 2:23 [PATCH bpf-next v2 0/3] libbpf: fix fuzzer-reported issues Shung-Hsi Yu
2022-10-12 2:23 ` [PATCH bpf-next v2 1/3] libbpf: use elf_getshdrnum() instead of e_shnum Shung-Hsi Yu
2022-10-12 2:23 ` [PATCH bpf-next v2 2/3] libbpf: deal with section with no data gracefully Shung-Hsi Yu
2022-10-12 2:23 ` [PATCH bpf-next v2 3/3] libbpf: fix null-pointer dereference in find_prog_by_sec_insn() Shung-Hsi Yu
2022-10-13 16:00 ` patchwork-bot+netdevbpf [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=166567681973.4134.13920189690256469312.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=shung-hsi.yu@suse.com \
--cc=song@kernel.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.