linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Tomislav Požega" <pozega.tomislav@gmail.com>
Cc: linux-wireless@vger.kernel.org, kvalo@codeaurora.org,
	daniel@makrotopia.org
Subject: Re: [PATCH 2/2] rt2x00: enable experimental MFP with HW crypt
Date: Wed, 13 Mar 2019 10:12:53 +0100	[thread overview]
Message-ID: <20190313091252.GB2663@redhat.com> (raw)
In-Reply-To: <1552417902-11040-2-git-send-email-pozega.tomislav@gmail.com>

On Tue, Mar 12, 2019 at 08:11:42PM +0100, Tomislav Požega wrote:
> MFP can work with enabled HW crypt engine, but in this case
> available bandwidth is reduced at least when connecting to
> Archer C7 (QCA9558). Enable the feature for known to work chipsets-
> MT7620, RT3070 and RT5390. Userspace setting for ieee80211w should
> default to 0 in order to prevent unintentional bandwidth drop.
> 
> Signed-off-by: Tomislav Po?ega <pozega.tomislav@gmail.com>
> ---
>  drivers/net/wireless/ralink/rt2x00/rt2800lib.c |   11 +++++++----
>  1 files changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
> index a03b528..bb8204d 100644
> --- a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
> @@ -9326,6 +9326,13 @@ static int rt2800_probe_hw_mode(struct rt2x00_dev *rt2x00dev)
>  	ieee80211_hw_set(rt2x00dev->hw, SIGNAL_DBM);
>  	ieee80211_hw_set(rt2x00dev->hw, SUPPORTS_PS);
>  
> +	/* Experimental: Set MFP with HW crypto enabled. */
> +	if (rt2x00_rt(rt2x00dev, RT3070) || rt2x00_rt(rt2x00dev, RT5390) ||
> +	    rt2x00_rt(rt2x00dev, RT6352))
> +		ieee80211_hw_set(rt2x00dev->hw, MFP_CAPABLE);

Is not that we support MFP in hardware. We just return -EOPNOTSUPP
in rt2x00mac_set_key() when mac80211 will try to set MFP ciphers
(since rt2x00crypto_key_to_cipher() will return CIPHER_NONE) and
we fallback to software encryption.

Please repost patch that enable MFP unconditionally with
'Cc: stable@vger.kernel.org' tag.

Stanislaw

  reply	other threads:[~2019-03-13  9:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 19:11 [PATCH 1/2] rt2x00: code-style fix in rt2800usb.c Tomislav Požega
2019-03-12 19:11 ` [PATCH 2/2] rt2x00: enable experimental MFP with HW crypt Tomislav Požega
2019-03-13  9:12   ` Stanislaw Gruszka [this message]
2019-03-13 13:02     ` Tom Psyborg
2019-03-13 13:09       ` Stanislaw Gruszka
2019-03-13 13:48         ` Tom Psyborg
2019-03-13 14:06           ` Stanislaw Gruszka
2019-03-13 14:41             ` Tom Psyborg
2019-03-13 15:50               ` Stanislaw Gruszka
2019-03-14 14:02                 ` Tom Psyborg
2019-03-14 14:13                   ` Stanislaw Gruszka
2019-03-25 14:25                   ` Stanislaw Gruszka
2019-03-26  1:54                     ` Tom Psyborg
2019-03-26  6:16                       ` Stanislaw Gruszka
2019-03-26  8:13                         ` Tom Psyborg
2019-03-26 10:41               ` Felix Fietkau
2019-03-26 11:35                 ` Stanislaw Gruszka

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=20190313091252.GB2663@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=daniel@makrotopia.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pozega.tomislav@gmail.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;
as well as URLs for NNTP newsgroup(s).