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, martin.lau@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/6] BPF Refcount followups 2: owner field
Date: Wed, 19 Jul 2023 00:30:22 +0000 [thread overview]
Message-ID: <168972662295.5728.6737046050379982493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230718083813.3416104-1-davemarchevsky@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 18 Jul 2023 01:38:07 -0700 you wrote:
> This series adds an 'owner' field to bpf_{list,rb}_node structs, to be
> used by the runtime to determine whether insertion or removal operations
> are valid in shared ownership scenarios. Both the races which the series
> fixes and the fix itself are inspired by Kumar's suggestions in [0].
>
> Aside from insertion and removal having more reasons to fail, there are
> no user-facing changes as a result of this series.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/6,DONOTAPPLY] Revert "bpf: Disable bpf_refcount_acquire kfunc calls until race conditions are fixed"
(no matching commit)
- [v2,bpf-next,2/6] bpf: Introduce internal definitions for UAPI-opaque bpf_{rb,list}_node
https://git.kernel.org/bpf/bpf-next/c/0a1f7bfe35a3
- [v2,bpf-next,3/6] bpf: Add 'owner' field to bpf_{list,rb}_node
https://git.kernel.org/bpf/bpf-next/c/c3c510ce431c
- [v2,bpf-next,4/6] selftests/bpf: Add rbtree test exercising race which 'owner' field prevents
https://git.kernel.org/bpf/bpf-next/c/fdf48dc2d054
- [v2,bpf-next,5/6] selftests/bpf: Disable newly-added 'owner' field test until refcount re-enabled
https://git.kernel.org/bpf/bpf-next/c/f3514a5d6740
- [v2,bpf-next,6/6,DONOTAPPLY] Revert "selftests/bpf: Disable newly-added 'owner' field test until refcount re-enabled"
(no matching commit)
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:[~2023-07-19 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 8:38 [PATCH v2 bpf-next 0/6] BPF Refcount followups 2: owner field Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 1/6] [DONOTAPPLY] Revert "bpf: Disable bpf_refcount_acquire kfunc calls until race conditions are fixed" Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 2/6] bpf: Introduce internal definitions for UAPI-opaque bpf_{rb,list}_node Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 3/6] bpf: Add 'owner' field to bpf_{list,rb}_node Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 4/6] selftests/bpf: Add rbtree test exercising race which 'owner' field prevents Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 5/6] selftests/bpf: Disable newly-added 'owner' field test until refcount re-enabled Dave Marchevsky
2023-07-18 8:38 ` [PATCH v2 bpf-next 6/6] [DONOTAPPLY] Revert "selftests/bpf: Disable newly-added 'owner' field test until refcount re-enabled" Dave Marchevsky
2023-07-19 0:30 ` 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=168972662295.5728.6737046050379982493.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=martin.lau@kernel.org \
/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).