Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	cel@kernel.org, donald.hunter@gmail.com,
	kernel-tls-handshake@lists.linux.dev
Subject: Re: [PATCH net-next 1/2] netlink: specs: handshake: type the remaining key serials s32
Date: Wed, 09 Sep 2026 21:00:12 +0000	[thread overview]
Message-ID: <178898761238.1057294.17887063472618531866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904190410.3864660-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  4 Sep 2026 12:04:09 -0700 you wrote:
> include/linux/key.h has "typedef int32_t key_serial_t" and commit
> 160f404495aa ("handshake: Fix sign of key_serial_t fields") converted
> x509.cert and x509.privkey to s32, but accept.peer-identity,
> accept.keyring and done.remote-auth were left as u32 - the same
> quantity typed both ways inside one family, and a generated user space
> struct with __s32 cert next to __u32 keyring. All three come from
> key_serial_t storage in net/handshake/tlshd.c (treq->th_peerid[],
> treq->th_keyring), and special keyrings are legitimately negative
> (KEY_SPEC_PROCESS_KEYRING is -2).
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] netlink: specs: handshake: type the remaining key serials s32
    https://git.kernel.org/netdev/net-next/c/f5134d734770
  - [net-next,2/2] netlink: specs: handshake: do not accept the handler-class sentinel
    https://git.kernel.org/netdev/net-next/c/fd0291fad9e7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-09 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 19:04 [PATCH net-next 1/2] netlink: specs: handshake: type the remaining key serials s32 Jakub Kicinski
2026-09-04 19:04 ` [PATCH net-next 2/2] netlink: specs: handshake: do not accept the handler-class sentinel Jakub Kicinski
2026-09-06 20:19   ` Asbjørn Sloth Tønnesen
2026-09-06 20:23 ` [PATCH net-next 1/2] netlink: specs: handshake: type the remaining key serials s32 Asbjørn Sloth Tønnesen
2026-09-06 23:35   ` Chuck Lever
2026-09-09 21: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=178898761238.1057294.17887063472618531866.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cel@kernel.org \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernel-tls-handshake@lists.linux.dev \
    --cc=kuba@kernel.org \
    --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