From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: bpf@vger.kernel.org, jakub@cloudflare.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: sockmap, fix preempt_rt splat when using raw_spin_lock_t
Date: Wed, 30 Aug 2023 08:10:21 +0000 [thread overview]
Message-ID: <169338302170.9000.3133905629277230133.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230830053517.166611-1-john.fastabend@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 29 Aug 2023 22:35:17 -0700 you wrote:
> Sockmap and sockhash maps are a collection of psocks that are
> objects representing a socket plus a set of metadata needed
> to manage the BPF programs associated with the socket. These
> maps use the stab->lock to protect from concurrent operations
> on the maps, e.g. trying to insert to objects into the array
> at the same time in the same slot. Additionally, a sockhash map
> has a bucket lock to protect iteration and insert/delete into
> the hash entry.
>
> [...]
Here is the summary with links:
- [bpf] bpf: sockmap, fix preempt_rt splat when using raw_spin_lock_t
https://git.kernel.org/bpf/bpf/c/35d2b7ffffc1
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-08-30 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 5:35 [PATCH bpf] bpf: sockmap, fix preempt_rt splat when using raw_spin_lock_t John Fastabend
2023-08-30 8:03 ` Daniel Borkmann
2023-08-30 8: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=169338302170.9000.3133905629277230133.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--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 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).