From: patchwork-bot+netdevbpf@kernel.org
To: Aditi Ghag <aditi.ghag@isovalent.com>
Cc: bpf@vger.kernel.org, kafai@fb.com, sdf@google.com
Subject: Re: [PATCH v9 bpf-next 0/9] bpf: Add socket destroy capability
Date: Sat, 20 May 2023 06:00:22 +0000 [thread overview]
Message-ID: <168456242263.5388.13008610099434399970.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230519225157.760788-1-aditi.ghag@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 19 May 2023 22:51:48 +0000 you wrote:
> This patch set adds the capability to destroy sockets in BPF. We plan to
> use the capability in Cilium to force client sockets to reconnect when
> their remote load-balancing backends are deleted. The other use case is
> on-the-fly policy enforcement where existing socket connections
> prevented by policies need to be terminated.
>
> The use cases, and more details around
> the selected approach were presented at LPC 2022 -
> https://lpc.events/event/16/contributions/1358/.
> RFC discussion -
> https://lore.kernel.org/netdev/CABG=zsBEh-P4NXk23eBJw7eajB5YJeRS7oPXnTAzs=yob4EMoQ@mail.gmail.com/T/#u.
> v8 patch series -
> https://lore.kernel.org/bpf/20230517175359.527917-1-aditi.ghag@isovalent.com/
>
> [...]
Here is the summary with links:
- [v9,bpf-next,1/9] bpf: tcp: Avoid taking fast sock lock in iterator
https://git.kernel.org/bpf/bpf-next/c/9378096e8a65
- [v9,bpf-next,2/9] udp: seq_file: Helper function to match socket attributes
https://git.kernel.org/bpf/bpf-next/c/f44b1c515833
- [v9,bpf-next,3/9] bpf: udp: Encapsulate logic to get udp table
https://git.kernel.org/bpf/bpf-next/c/7625d2e9741c
- [v9,bpf-next,4/9] udp: seq_file: Remove bpf_seq_afinfo from udp_iter_state
https://git.kernel.org/bpf/bpf-next/c/e4fe1bf13e09
- [v9,bpf-next,5/9] bpf: udp: Implement batching for sockets iterator
https://git.kernel.org/bpf/bpf-next/c/c96dac8d369f
- [v9,bpf-next,6/9] bpf: Add kfunc filter function to 'struct btf_kfunc_id_set'
https://git.kernel.org/bpf/bpf-next/c/e924e80ee6a3
- [v9,bpf-next,7/9] bpf: Add bpf_sock_destroy kfunc
https://git.kernel.org/bpf/bpf-next/c/4ddbcb886268
- [v9,bpf-next,8/9] selftests/bpf: Add helper to get port using getsockname
https://git.kernel.org/bpf/bpf-next/c/176ba657e6aa
- [v9,bpf-next,9/9] selftests/bpf: Test bpf_sock_destroy
https://git.kernel.org/bpf/bpf-next/c/1a8bc2299f40
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-05-20 6:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 22:51 [PATCH v9 bpf-next 0/9] bpf: Add socket destroy capability Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 1/9] bpf: tcp: Avoid taking fast sock lock in iterator Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 2/9] udp: seq_file: Helper function to match socket attributes Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 3/9] bpf: udp: Encapsulate logic to get udp table Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 4/9] udp: seq_file: Remove bpf_seq_afinfo from udp_iter_state Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 5/9] bpf: udp: Implement batching for sockets iterator Aditi Ghag
2023-09-20 0:38 ` Martin KaFai Lau
2023-09-20 17:16 ` Aditi Ghag
2023-09-25 23:34 ` Aditi Ghag
2023-09-26 5:02 ` Martin KaFai Lau
2023-09-26 16:07 ` Aditi Ghag
2023-10-24 22:50 ` Aditi Ghag
2023-09-26 5:07 ` Martin KaFai Lau
2023-05-19 22:51 ` [PATCH v9 bpf-next 6/9] bpf: Add kfunc filter function to 'struct btf_kfunc_id_set' Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 7/9] bpf: Add bpf_sock_destroy kfunc Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 8/9] selftests/bpf: Add helper to get port using getsockname Aditi Ghag
2023-05-19 22:51 ` [PATCH v9 bpf-next 9/9] selftests/bpf: Test bpf_sock_destroy Aditi Ghag
2023-05-20 6:00 ` 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=168456242263.5388.13008610099434399970.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aditi.ghag@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=kafai@fb.com \
--cc=sdf@google.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