Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Apr 2024 14:32:11 -0400
From:      Cheng Cui <cc@freebsd.org>
To:        wireless@freebsd.org
Subject:   Weekly Development report(Apr 08 ~ Apr 12) on the iwlwifi WiFi project
Message-ID:  <CAGaXuiJ9H9E6H8OOtKg9bDoYpyk%2B2_gQ7bot0HF58a5ytEiPgg@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
--00000000000024dd84061626d9fa
Content-Type: text/plain; charset="UTF-8"

Still working on the HW key/encryption/decryption support under the
`LKPI_80211_HW_CRYPTO` block.


   - This week I was mainly testing different ideas and digging up
   different code paths to see any clue that leads to HW crypto offload
   malfunction.


   1. Firstly, I figured out how to reproduce the malfunction in Linux
      kernel, with the way to nullify info->control.hw_key right before
      iwl_mvm_set_tx_params() inside iwl_mvm_tx_mpdu(). I added this
info in the
      tracking PR 277996
      <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277996>.
      2. We(adrian@ bz@ and me) are in sync with the issue. Adrian is very
      kind and introduced some related work background.
      3. So far, some missing flags, e.g. IEEE80211_KEY_FLAG_PAIRWISE
      or ieee80211_tx_info_flags do not help. And my blind guess of
      shrinking ieee80211_tx_info size to match Linux skb->cb 48 Byte size does
      not seem to work either.

Will again dig up the driver hw key setup path in Linux and investigate.

-- 
Best Regards,
Cheng Cui

--00000000000024dd84061626d9fa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Still working on the HW key/encryption/decryption support =
under the `LKPI_80211_HW_CRYPTO` block.<div><br></div><div><ul><li>This wee=
k I was mainly testing different ideas and digging up different=C2=A0code p=
aths to see any clue that leads to HW crypto offload malfunction.<br></li><=
/ul><ol><ol><li>Firstly, I figured out how to reproduce the malfunction in =
Linux kernel, with the way to=C2=A0nullify info-&gt;control.hw_key right be=
fore iwl_mvm_set_tx_params() inside iwl_mvm_tx_mpdu(). I added this info in=
 the tracking PR=C2=A0<a href=3D"https://bugs.freebsd.org/bugzilla/show_bug=
.cgi?id=3D277996" target=3D"_blank">277996</a>.</li><li>We(adrian@ bz@ and =
me) are in sync with the issue. Adrian is very kind and introduced some rel=
ated work background.</li><li>So far, some missing flags, e.g.=C2=A0IEEE802=
11_KEY_FLAG_PAIRWISE or=C2=A0ieee80211_tx_info_flags do not help. And my bl=
ind guess of shrinking=C2=A0ieee80211_tx_info size to match Linux skb-&gt;c=
b 48 Byte=C2=A0size does not seem to work either.</li></ol></ol>Will again =
dig up the driver hw key setup path in Linux and investigate.<br><div><br><=
/div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" =
class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"lt=
r"><div></div>Best Regards,<div>Cheng Cui</div></div></div></div></div>

--00000000000024dd84061626d9fa--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGaXuiJ9H9E6H8OOtKg9bDoYpyk%2B2_gQ7bot0HF58a5ytEiPgg>