From: patchwork-bot+netdevbpf@kernel.org
To: Emeel Hakim <ehakim@nvidia.com>
Cc: sd@queasysnail.net, dsahern@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v3 1/1] macsec: Fix Macsec replay protection
Date: Sun, 15 Jan 2023 19:50:16 +0000 [thread overview]
Message-ID: <167381221625.28915.16674838611784337050.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230111073259.19723-1-ehakim@nvidia.com>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Wed, 11 Jan 2023 09:32:59 +0200 you wrote:
> From: Emeel Hakim <ehakim@nvidia.com>
>
> Currently when configuring macsec with replay protection,
> replay protection and window gets a default value of -1,
> the above is leading to passing replay protection and
> replay window attributes to the kernel while replay is
> explicitly set to off, leading for an invalid argument
> error when configured with extended packet number (XPN).
> since the default window value which is 0xFFFFFFFF is
> passed to the kernel and while XPN is configured the above
> value is an invalid window value.
>
> [...]
Here is the summary with links:
- [iproute2,v3,1/1] macsec: Fix Macsec replay protection
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=16ed170abf4b
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-01-15 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 7:32 [PATCH iproute2 v3 1/1] macsec: Fix Macsec replay protection ehakim
2023-01-11 11:15 ` Sabrina Dubroca
2023-01-15 19: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=167381221625.28915.16674838611784337050.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=ehakim@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).