From: Sabrina Dubroca <sd@queasysnail.net>
To: Davide Caratti <dcaratti@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCH net 0/3] macsec: fix configurable ICV length
Date: Mon, 25 Jul 2016 12:09:32 +0200 [thread overview]
Message-ID: <20160725100932.GA4847@bistromath.localdomain> (raw)
In-Reply-To: <cover.1469191850.git.dcaratti@redhat.com>
2016-07-22, 15:07:55 +0200, Davide Caratti wrote:
> This series provides a fix for macsec configurable ICV length. The
> maximum length of ICV element has been made compliant to IEEE 802.1AE,
> and error reporting in case of cipher suite configuration failure has been
> improved. Finally, a test has been added to netlink verify() callback in
> order to avoid creation of macsec interfaces having user-provided ICV length
> values that are not supported by the cipher suite.
>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
>
> Davide Caratti (3):
> macsec: limit ICV length to 16 octets
> macsec: fix error codes when a SA is created
> macsec: validate ICV length on link creation
>
> drivers/net/macsec.c | 76 ++++++++++++++++++++++++++++--------------
> include/uapi/linux/if_macsec.h | 2 ++
> 2 files changed, 53 insertions(+), 25 deletions(-)
Acked-by: Sabrina Dubroca <sd@queasysnail.net>
--
Sabrina
next prev parent reply other threads:[~2016-07-25 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:07 [PATCH net 0/3] macsec: fix configurable ICV length Davide Caratti
2016-07-22 13:07 ` [PATCH net 1/3] macsec: limit ICV length to 16 octets Davide Caratti
2016-07-22 13:07 ` [PATCH net 2/3] macsec: fix error codes when a SA is created Davide Caratti
2016-07-22 13:07 ` [PATCH net 3/3] macsec: validate ICV length on link creation Davide Caratti
2016-07-25 10:09 ` Sabrina Dubroca [this message]
2016-07-25 17:55 ` [PATCH net 0/3] macsec: fix configurable ICV length David Miller
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=20160725100932.GA4847@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/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).