public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
	herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/8] xfrm: clear trailing padding in build_polexpire()
Date: Thu, 09 Apr 2026 02:00:22 +0000	[thread overview]
Message-ID: <177570002230.953143.9369644013047810016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408095925.253681-2-steffen.klassert@secunet.com>

Hello:

This series was applied to netdev/net.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:

On Wed, 8 Apr 2026 11:58:57 +0200 you wrote:
> From: Yasuaki Torimaru <yasuakitorimaru@gmail.com>
> 
> build_expire() clears the trailing padding bytes of struct
> xfrm_user_expire after setting the hard field via memset_after(),
> but the analogous function build_polexpire() does not do this for
> struct xfrm_user_polexpire.
> 
> [...]

Here is the summary with links:
  - [1/8] xfrm: clear trailing padding in build_polexpire()
    https://git.kernel.org/netdev/net/c/71a98248c63c
  - [2/8] xfrm: account XFRMA_IF_ID in aevent size calculation
    https://git.kernel.org/netdev/net/c/7081d46d3231
  - [3/8] xfrm: Wait for RCU readers during policy netns exit
    https://git.kernel.org/netdev/net/c/069daad4f2ae
  - [4/8] xfrm: hold dev ref until after transport_finish NF_HOOK
    https://git.kernel.org/netdev/net/c/1c428b038400
  - [5/8] xfrm: fix refcount leak in xfrm_migrate_policy_find
    https://git.kernel.org/netdev/net/c/83317cce60a0
  - [6/8] xfrm_user: fix info leak in build_mapping()
    https://git.kernel.org/netdev/net/c/1beb76b2053b
  - [7/8] xfrm_user: fix info leak in build_report()
    https://git.kernel.org/netdev/net/c/d10119968d0e
  - [8/8] net: af_key: zero aligned sockaddr tail in PF_KEY exports
    https://git.kernel.org/netdev/net/c/426c355742f0

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



  reply	other threads:[~2026-04-09  2:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  9:58 [PATCH 0/8] pull request (net): ipsec 2026-04-08 Steffen Klassert
2026-04-08  9:58 ` [PATCH 1/8] xfrm: clear trailing padding in build_polexpire() Steffen Klassert
2026-04-09  2:00   ` patchwork-bot+netdevbpf [this message]
2026-04-08  9:58 ` [PATCH 2/8] xfrm: account XFRMA_IF_ID in aevent size calculation Steffen Klassert
2026-04-08  9:58 ` [PATCH 3/8] xfrm: Wait for RCU readers during policy netns exit Steffen Klassert
2026-04-08  9:59 ` [PATCH 4/8] xfrm: hold dev ref until after transport_finish NF_HOOK Steffen Klassert
2026-04-08  9:59 ` [PATCH 5/8] xfrm: fix refcount leak in xfrm_migrate_policy_find Steffen Klassert
2026-04-08  9:59 ` [PATCH 6/8] xfrm_user: fix info leak in build_mapping() Steffen Klassert
2026-04-08  9:59 ` [PATCH 7/8] xfrm_user: fix info leak in build_report() Steffen Klassert
2026-04-08  9:59 ` [PATCH 8/8] net: af_key: zero aligned sockaddr tail in PF_KEY exports Steffen Klassert

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=177570002230.953143.9369644013047810016.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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