From: patchwork-bot+netdevbpf@kernel.org
To: Youlin Li <liulin063@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf 1/2 v2] bpf: Fix wrong reg type conversion in release_reference()
Date: Thu, 03 Nov 2022 23:50:15 +0000 [thread overview]
Message-ID: <166751941531.11927.6923605690119797378.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221103093440.3161-1-liulin063@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 3 Nov 2022 17:34:39 +0800 you wrote:
> Some helper functions will allocate memory. To avoid memory leaks, the
> verifier requires the eBPF program to release these memories by calling
> the corresponding helper functions.
>
> When a resource is released, all pointer registers corresponding to the
> resource should be invalidated. The verifier use release_references() to
> do this job, by apply __mark_reg_unknown() to each relevant register.
>
> [...]
Here is the summary with links:
- [bpf,1/2,v2] bpf: Fix wrong reg type conversion in release_reference()
https://git.kernel.org/bpf/bpf/c/f1db20814af5
- [bpf,2/2] selftests/bpf: Add verifier test for release_reference()
https://git.kernel.org/bpf/bpf/c/475244f5e06b
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-11-03 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 9:34 [PATCH bpf 1/2 v2] bpf: Fix wrong reg type conversion in release_reference() Youlin Li
2022-11-03 9:34 ` [PATCH bpf 2/2] selftests/bpf: Add verifier test for release_reference() Youlin Li
2022-11-03 23:50 ` 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=166751941531.11927.6923605690119797378.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=liulin063@gmail.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