From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kernel-team@fb.com, yhs@meta.com, yhs@fb.com,
memxor@gmail.com
Subject: Re: [PATCH v2 bpf-next 1/2] bpf: Fix release_on_unlock release logic for multiple refs
Date: Fri, 02 Dec 2022 03:50:15 +0000 [thread overview]
Message-ID: <166995301598.8499.11538019809348261735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221201183406.1203621-1-davemarchevsky@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 1 Dec 2022 10:34:05 -0800 you wrote:
> Consider a verifier state with three acquired references, all with
> release_on_unlock = true:
>
> idx 0 1 2
> state->refs = [2 4 6]
>
> (with 2, 4, and 6 being the ref ids).
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/2] bpf: Fix release_on_unlock release logic for multiple refs
https://git.kernel.org/bpf/bpf-next/c/1f82dffc10ff
- [v2,bpf-next,2/2] selftests/bpf: Validate multiple ref release_on_unlock logic
https://git.kernel.org/bpf/bpf-next/c/78b037bd402d
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-12-02 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 18:34 [PATCH v2 bpf-next 1/2] bpf: Fix release_on_unlock release logic for multiple refs Dave Marchevsky
2022-12-01 18:34 ` [PATCH v2 bpf-next 2/2] selftests/bpf: Validate multiple ref release_on_unlock logic Dave Marchevsky
2022-12-02 3:21 ` Yonghong Song
2022-12-02 0:10 ` [PATCH v2 bpf-next 1/2] bpf: Fix release_on_unlock release logic for multiple refs Yonghong Song
2022-12-02 3: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=166995301598.8499.11538019809348261735.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=davemarchevsky@fb.com \
--cc=kernel-team@fb.com \
--cc=memxor@gmail.com \
--cc=yhs@fb.com \
--cc=yhs@meta.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.