From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, brauner@kernel.org,
chuck.lever@oracle.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 00/14] rxrpc, afs: Add AFS GSSAPI security class to AF_RXRPC and kafs
Date: Tue, 15 Apr 2025 00:50:39 +0000 [thread overview]
Message-ID: <174467823949.2089736.14930552033478134698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250411095303.2316168-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 11 Apr 2025 10:52:45 +0100 you wrote:
> Here's a set of patches to add basic support for the AFS GSSAPI security
> class to AF_RXRPC and kafs. It provides transport security for keys that
> match the security index 6 (YFS) for connections to the AFS fileserver and
> VL server.
>
> Note that security index 4 (OpenAFS) can also be supported using this, but
> it needs more work as it's slightly different.
>
> [...]
Here is the summary with links:
- [net-next,v3,01/14] rxrpc: kdoc: Update function descriptions and add link from rxrpc.rst
https://git.kernel.org/netdev/net-next/c/28a79fc9b03e
- [net-next,v3,02/14] rxrpc: Pull out certain app callback funcs into an ops table
https://git.kernel.org/netdev/net-next/c/23738cc80483
- [net-next,v3,03/14] rxrpc: Remove some socket lock acquire/release annotations
https://git.kernel.org/netdev/net-next/c/019c8433eb29
- [net-next,v3,04/14] rxrpc: Allow CHALLENGEs to the passed to the app for a RESPONSE
https://git.kernel.org/netdev/net-next/c/5800b1cf3fd8
- [net-next,v3,05/14] rxrpc: Add the security index for yfs-rxgk
https://git.kernel.org/netdev/net-next/c/01af64269751
- [net-next,v3,06/14] rxrpc: Add YFS RxGK (GSSAPI) security class
https://git.kernel.org/netdev/net-next/c/0ca100ff4df6
- [net-next,v3,07/14] rxrpc: rxgk: Provide infrastructure and key derivation
https://git.kernel.org/netdev/net-next/c/c86f9b963dc6
- [net-next,v3,08/14] rxrpc: rxgk: Implement the yfs-rxgk security class (GSSAPI)
https://git.kernel.org/netdev/net-next/c/9d1d2b59341f
- [net-next,v3,09/14] rxrpc: rxgk: Implement connection rekeying
https://git.kernel.org/netdev/net-next/c/7a7513a3081c
- [net-next,v3,10/14] rxrpc: Allow the app to store private data on peer structs
https://git.kernel.org/netdev/net-next/c/b794dc17cdd0
- [net-next,v3,11/14] rxrpc: Display security params in the afs_cb_call tracepoint
https://git.kernel.org/netdev/net-next/c/d03539d5c2de
- [net-next,v3,12/14] afs: Use rxgk RESPONSE to pass token for callback channel
https://git.kernel.org/netdev/net-next/c/d98c317fd9aa
- [net-next,v3,13/14] rxrpc: Add more CHALLENGE/RESPONSE packet tracing
https://git.kernel.org/netdev/net-next/c/fba6995798c6
- [net-next,v3,14/14] rxrpc: rxperf: Add test RxGK server keys
https://git.kernel.org/netdev/net-next/c/aa2199088a39
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:[~2025-04-15 0:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:52 [PATCH net-next v3 00/14] rxrpc, afs: Add AFS GSSAPI security class to AF_RXRPC and kafs David Howells
2025-04-11 9:52 ` [PATCH net-next v3 01/14] rxrpc: kdoc: Update function descriptions and add link from rxrpc.rst David Howells
2025-04-11 9:52 ` [PATCH net-next v3 02/14] rxrpc: Pull out certain app callback funcs into an ops table David Howells
2025-04-11 9:52 ` [PATCH net-next v3 03/14] rxrpc: Remove some socket lock acquire/release annotations David Howells
2025-04-11 9:52 ` [PATCH net-next v3 04/14] rxrpc: Allow CHALLENGEs to the passed to the app for a RESPONSE David Howells
2025-04-11 9:52 ` [PATCH net-next v3 05/14] rxrpc: Add the security index for yfs-rxgk David Howells
2025-04-11 9:52 ` [PATCH net-next v3 06/14] rxrpc: Add YFS RxGK (GSSAPI) security class David Howells
2025-04-11 9:52 ` [PATCH net-next v3 07/14] rxrpc: rxgk: Provide infrastructure and key derivation David Howells
2025-04-11 9:52 ` [PATCH net-next v3 08/14] rxrpc: rxgk: Implement the yfs-rxgk security class (GSSAPI) David Howells
2025-04-11 9:52 ` [PATCH net-next v3 09/14] rxrpc: rxgk: Implement connection rekeying David Howells
2025-04-11 9:52 ` [PATCH net-next v3 10/14] rxrpc: Allow the app to store private data on peer structs David Howells
2025-04-11 9:52 ` [PATCH net-next v3 11/14] rxrpc: Display security params in the afs_cb_call tracepoint David Howells
2025-04-11 9:52 ` [PATCH net-next v3 12/14] afs: Use rxgk RESPONSE to pass token for callback channel David Howells
2025-04-11 9:52 ` [PATCH net-next v3 13/14] rxrpc: Add more CHALLENGE/RESPONSE packet tracing David Howells
2025-04-11 9:52 ` [PATCH net-next v3 14/14] rxrpc: rxperf: Add test RxGK server keys David Howells
2025-04-15 0: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=174467823949.2089736.14930552033478134698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).