From: Sabrina Dubroca <sd@queasysnail.net>
To: Tobias Brunner <tobias@strongswan.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net] macsec: Fix header length if SCI is added if explicitily disabled
Date: Mon, 24 Oct 2016 13:28:22 +0200 [thread overview]
Message-ID: <20161024112822.GA28497@bistromath.localdomain> (raw)
In-Reply-To: <bfb9f7ef-39b1-269f-48de-d7caf5c54c2f@strongswan.org>
2016-10-21, 13:11:37 +0200, Tobias Brunner wrote:
> Even if sending SCIs is explicitly disabled, the code that creates the
> Security Tag might still decide to add it (e.g. if multiple RX SCs are
> defined on the MACsec interface).
> But because the header length so far only depended on the configuration
> option the SCI might not actually have ended up in the packet, while the
> SC flag in the TCI field of the Security Tag was still set, resulting
> in invalid MACsec frames.
Or overwriting the original frame's contents (ethertype and eg
beginning of the IP header) if !encrypt.
Fixes: c09440f7dcb3 ("macsec: introduce IEEE 802.1AE driver")
[snip]
> @@ -440,12 +448,12 @@ static void macsec_fill_sectag(struct macsec_eth_header *h,
> const struct macsec_secy *secy, u32 pn)
> {
> const struct macsec_tx_sc *tx_sc = &secy->tx_sc;
> + bool sci_present = send_sci(secy);
You're already computing this in macsec_encrypt() just before calling
macsec_fill_sectag(), so you could pass it as argument instead of
recomputing it.
Other than that, LGTM, thanks!
--
Sabrina
next prev parent reply other threads:[~2016-10-24 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:11 [PATCH net] macsec: Fix header length if SCI is added if explicitily disabled Tobias Brunner
2016-10-24 11:28 ` Sabrina Dubroca [this message]
2016-10-24 13:32 ` Tobias Brunner
2016-10-24 13:38 ` Sabrina Dubroca
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=20161024112822.GA28497@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tobias@strongswan.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).