public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Antoine Tenart <atenart@kernel•org>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
	edumazet@google•com, sd@queasysnail•net, irusskikh@marvell•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH net 0/2] macsec: clear encryption keys in h/w drivers
Date: Thu, 10 Nov 2022 11:10:14 +0000	[thread overview]
Message-ID: <166807861467.26157.1927496799417807435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221108153459.811293-1-atenart@kernel.org>

Hello:

This series was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat•com>:

On Tue,  8 Nov 2022 16:34:57 +0100 you wrote:
> Hello,
> 
> Commit aaab73f8fba4 ("macsec: clear encryption keys from the stack after
> setting up offload") made sure to clean encryption keys from the stack
> after setting up offloading but some h/w drivers did a copy of the key
> which need to be zeroed as well.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net: phy: mscc: macsec: clear encryption keys when freeing a flow
    https://git.kernel.org/netdev/net/c/1b16b3fdf675
  - [net,2/2] net: atlantic: macsec: clear encryption keys from the stack
    https://git.kernel.org/netdev/net/c/879785def0f5

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



      parent reply	other threads:[~2022-11-10 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 15:34 [PATCH net 0/2] macsec: clear encryption keys in h/w drivers Antoine Tenart
2022-11-08 15:34 ` [PATCH net 1/2] net: phy: mscc: macsec: clear encryption keys when freeing a flow Antoine Tenart
2022-11-08 15:34 ` [PATCH net 2/2] net: atlantic: macsec: clear encryption keys from the stack Antoine Tenart
2022-11-09  9:54 ` [EXT] [PATCH net 0/2] macsec: clear encryption keys in h/w drivers Igor Russkikh
2022-11-10 11: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=166807861467.26157.1927496799417807435.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=atenart@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=irusskikh@marvell$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sd@queasysnail$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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