All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Carl Huang <quic_cjhuang@quicinc.com>
Cc: <ath11k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 6/6] ath11k: support GTK rekey offload
Date: Tue, 22 Feb 2022 15:54:59 +0200	[thread overview]
Message-ID: <875yp7vwek.fsf@kernel.org> (raw)
In-Reply-To: <1644308006-22784-7-git-send-email-quic_cjhuang@quicinc.com> (Carl Huang's message of "Tue, 8 Feb 2022 16:13:26 +0800")

Carl Huang <quic_cjhuang@quicinc.com> writes:

> Host sets GTK related info to firmware before WoW is enabled, and
> gets rekey replay_count and then disables GTK rekey when WoW quits.
>
> Tested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
>
> Signed-off-by: Carl Huang <quic_cjhuang@quicinc.com>

[...]

> +static void ath11k_mac_op_set_rekey_data(struct ieee80211_hw *hw,
> +					 struct ieee80211_vif *vif,
> +					 struct cfg80211_gtk_rekey_data *data)
> +{
> +	struct ath11k *ar = hw->priv;
> +	struct ath11k_vif *arvif = ath11k_vif_to_arvif(vif);
> +	struct ath11k_rekey_data *rekey_data = &arvif->rekey_data;
> +
> +	ath11k_dbg(ar->ab, ATH11K_DBG_MAC, "Set rekey data vdev_id %d\n",
> +		   arvif->vdev_id);
> +	mutex_lock(&ar->conf_mutex);
> +
> +	memcpy(rekey_data->kck, data->kck, NL80211_KCK_LEN);
> +	memcpy(rekey_data->kek, data->kek, NL80211_KEK_LEN);
> +
> +	/* supplicant works on big-endian, converts to cpu-endian */
> +	rekey_data->replay_ctr = be64_to_cpu(get_unaligned((u64 *)data->replay_ctr));

This has a warning:

drivers/net/wireless/ath/ath11k/mac.c:8219:34: warning: cast to restricted __be64

In the pending branch I changed this to:

	/* The supplicant works on big-endian, the firmware expects it on
	 * little endian.
	 */
	rekey_data->replay_ctr = get_unaligned_be64(data->replay_ctr);

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Carl Huang <quic_cjhuang@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 6/6] ath11k: support GTK rekey offload
Date: Tue, 22 Feb 2022 15:54:59 +0200	[thread overview]
Message-ID: <875yp7vwek.fsf@kernel.org> (raw)
In-Reply-To: <1644308006-22784-7-git-send-email-quic_cjhuang@quicinc.com> (Carl Huang's message of "Tue, 8 Feb 2022 16:13:26 +0800")

Carl Huang <quic_cjhuang@quicinc.com> writes:

> Host sets GTK related info to firmware before WoW is enabled, and
> gets rekey replay_count and then disables GTK rekey when WoW quits.
>
> Tested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
>
> Signed-off-by: Carl Huang <quic_cjhuang@quicinc.com>

[...]

> +static void ath11k_mac_op_set_rekey_data(struct ieee80211_hw *hw,
> +					 struct ieee80211_vif *vif,
> +					 struct cfg80211_gtk_rekey_data *data)
> +{
> +	struct ath11k *ar = hw->priv;
> +	struct ath11k_vif *arvif = ath11k_vif_to_arvif(vif);
> +	struct ath11k_rekey_data *rekey_data = &arvif->rekey_data;
> +
> +	ath11k_dbg(ar->ab, ATH11K_DBG_MAC, "Set rekey data vdev_id %d\n",
> +		   arvif->vdev_id);
> +	mutex_lock(&ar->conf_mutex);
> +
> +	memcpy(rekey_data->kck, data->kck, NL80211_KCK_LEN);
> +	memcpy(rekey_data->kek, data->kek, NL80211_KEK_LEN);
> +
> +	/* supplicant works on big-endian, converts to cpu-endian */
> +	rekey_data->replay_ctr = be64_to_cpu(get_unaligned((u64 *)data->replay_ctr));

This has a warning:

drivers/net/wireless/ath/ath11k/mac.c:8219:34: warning: cast to restricted __be64

In the pending branch I changed this to:

	/* The supplicant works on big-endian, the firmware expects it on
	 * little endian.
	 */
	rekey_data->replay_ctr = get_unaligned_be64(data->replay_ctr);

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-02-22 13:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  8:13 [PATCH v3 0/6] ath11k: support WoW functionalities Carl Huang
2022-02-08  8:13 ` Carl Huang
2022-02-08  8:13 ` [PATCH v3 1/6] ath11k: Add basic " Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-08 10:55   ` kernel test robot
2022-02-08 12:15   ` kernel test robot
2022-02-08 20:55   ` Jeff Johnson
2022-02-08 20:55     ` Jeff Johnson
2022-02-10  6:43     ` Kalle Valo
2022-02-10  6:43       ` Kalle Valo
2022-02-10 11:39   ` Kalle Valo
2022-02-10 11:39     ` Kalle Valo
2022-02-22 12:54   ` Kalle Valo
2022-02-22 12:54     ` Kalle Valo
2022-02-22 13:59     ` Kalle Valo
2022-02-22 13:59       ` Kalle Valo
2022-02-22 14:28       ` Kalle Valo
2022-02-22 14:28         ` Kalle Valo
2022-02-24 16:09   ` Kalle Valo
2022-02-24 16:09     ` Kalle Valo
2022-03-18 15:37   ` Kalle Valo
2022-03-18 15:37     ` Kalle Valo
2022-02-08  8:13 ` [PATCH v3 2/6] ath11k: Add WoW net-detect functionality Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-08  8:13 ` [PATCH v3 3/6] ath11k: implement hardware data filter Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-08  8:13 ` [PATCH v3 4/6] ath11k: purge rx pktlog when entering WoW Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-08  8:13 ` [PATCH v3 5/6] ath11k: support ARP and NS offload Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-08  8:13 ` [PATCH v3 6/6] ath11k: support GTK rekey offload Carl Huang
2022-02-08  8:13   ` Carl Huang
2022-02-22 13:54   ` Kalle Valo [this message]
2022-02-22 13:54     ` Kalle Valo

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=875yp7vwek.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_cjhuang@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.