From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf 0/3] bpf: Fixes for bpf_sk_storage
Date: Wed, 06 Sep 2023 09:10:22 +0000 [thread overview]
Message-ID: <169399142241.26603.13283011863319569534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230901231129.578493-1-martin.lau@linux.dev>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 1 Sep 2023 16:11:26 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> This set has two fixes for bpf_sk_storage. Please see the individual
> patch for details.
>
> Martin KaFai Lau (3):
> bpf: bpf_sk_storage: Fix invalid wait context lockdep report
> bpf: bpf_sk_storage: Fix the missing uncharge in sk_omem_alloc
> selftests/bpf: Check bpf_sk_storage has uncharged sk_omem_alloc
>
> [...]
Here is the summary with links:
- [bpf,1/3] bpf: bpf_sk_storage: Fix invalid wait context lockdep report
https://git.kernel.org/bpf/bpf/c/a96a44aba556
- [bpf,2/3] bpf: bpf_sk_storage: Fix the missing uncharge in sk_omem_alloc
https://git.kernel.org/bpf/bpf/c/55d49f750b1c
- [bpf,3/3] selftests/bpf: Check bpf_sk_storage has uncharged sk_omem_alloc
https://git.kernel.org/bpf/bpf/c/a96d1cfb2da0
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-09-06 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 23:11 [PATCH bpf 0/3] bpf: Fixes for bpf_sk_storage Martin KaFai Lau
2023-09-01 23:11 ` [PATCH bpf 1/3] bpf: bpf_sk_storage: Fix invalid wait context lockdep report Martin KaFai Lau
2023-09-01 23:11 ` [PATCH bpf 2/3] bpf: bpf_sk_storage: Fix the missing uncharge in sk_omem_alloc Martin KaFai Lau
2023-09-01 23:11 ` [PATCH bpf 3/3] selftests/bpf: Check bpf_sk_storage has uncharged sk_omem_alloc Martin KaFai Lau
2023-09-06 9:10 ` 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=169399142241.26603.13283011863319569534.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=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.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 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.