<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/net/mac80211/mlme.c, branch v6.2</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v6.2</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v6.2'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2022-12-01T14:09:10+00:00</updated>
<entry>
<title>wifi: mac80211: don't parse multi-BSSID in assoc resp</title>
<updated>2022-12-01T14:09:10+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-10-14T16:56:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8950b5988a9a2957b4c2c6f20143dfc2a0230a74'/>
<id>urn:sha1:8950b5988a9a2957b4c2c6f20143dfc2a0230a74</id>
<content type='text'>
It's not valid to have the multiple BSSID element in the
association response (per 802.11 REVme D1.0), so don't
try to parse it there, but only in the fallback beacon
elements if needed.

The other case that was parsing association requests was
already changed in a previous commit.

Change-Id: I659d2ef1253e079cc71c46a017044e116e31c024
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'wireless/main' into wireless-next</title>
<updated>2022-10-10T09:03:43+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-10-10T09:03:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=dfd2d876b3fda1790bc0239ba4c6967e25d16e91'/>
<id>urn:sha1:dfd2d876b3fda1790bc0239ba4c6967e25d16e91</id>
<content type='text'>
Pull in wireless/main content since some new code would
otherwise conflict with it.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: don't clear DTIM period after setting it</title>
<updated>2022-10-07T13:24:24+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-09-15T12:57:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=cb04b5ef855c210a6e8e3e64fae9e2da9100f72e'/>
<id>urn:sha1:cb04b5ef855c210a6e8e3e64fae9e2da9100f72e</id>
<content type='text'>
Fix the code that sets the DTIM period to always propagate it
into link-&gt;conf-&gt;dtim_period and not overwrite it, while still
preferring to set it from the beacon data if available.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: mlme: mark assoc link in output</title>
<updated>2022-10-07T13:24:21+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-09-20T20:43:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7a693ce0033707a49e951769cc230ef870ff76a8'/>
<id>urn:sha1:7a693ce0033707a49e951769cc230ef870ff76a8</id>
<content type='text'>
It's useful to know which link was used for the association,
mark it when printing the links.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: check link ID in auth/assoc continuation</title>
<updated>2022-10-07T13:24:18+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-09-21T21:01:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=85176a3fcd9748558cff72d4cdff5465b8732282'/>
<id>urn:sha1:85176a3fcd9748558cff72d4cdff5465b8732282</id>
<content type='text'>
Ensure that the link ID matches in auth/assoc continuation,
otherwise we need to reset all the data.

Fixes: 81151ce462e5 ("wifi: mac80211: support MLO authentication/association with one link")
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: mlme: fix null-ptr deref on failed assoc</title>
<updated>2022-10-07T13:24:16+00:00</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2022-09-21T00:44:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=78a6a43aaf87180ec7425a2a90468e1b4d09a1ec'/>
<id>urn:sha1:78a6a43aaf87180ec7425a2a90468e1b4d09a1ec</id>
<content type='text'>
If association to an AP without a link 0 fails, then we crash in
tracing because it assumes that either ap_mld_addr or link 0 BSS
is valid, since we clear sdata-&gt;vif.valid_links and then don't
add the ap_mld_addr to the struct.

Since we clear also sdata-&gt;vif.cfg.ap_addr, keep a local copy of
it and assign it earlier, before clearing valid_links, to fix
this.

Fixes: 81151ce462e5 ("wifi: mac80211: support MLO authentication/association with one link")
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: advertise TWT requester only with HW support</title>
<updated>2022-10-07T13:24:08+00:00</updated>
<author>
<name>Haim Dreyfuss</name>
<email>haim.dreyfuss@intel.com</email>
</author>
<published>2022-09-11T19:01:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=0143ea09b63d58ed3e19ffdfc444cc23d8d877b6'/>
<id>urn:sha1:0143ea09b63d58ed3e19ffdfc444cc23d8d877b6</id>
<content type='text'>
Currently, we rely only on the AP capability. If the AP supports
TWT responder we will advertise TWT requester even if the driver
or HW doesn't support it. Fix this by checking the HW capability.

Signed-off-by: Haim Dreyfuss &lt;haim.dreyfuss@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: Process association status for affiliated links</title>
<updated>2022-10-07T13:23:58+00:00</updated>
<author>
<name>Ilan Peer</name>
<email>ilan.peer@intel.com</email>
</author>
<published>2022-09-08T08:31:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c2d052a3c41aa7815714a18911819efde0d7d384'/>
<id>urn:sha1:c2d052a3c41aa7815714a18911819efde0d7d384</id>
<content type='text'>
In case the AP returned a non success status for one of the links,
do not activate the link.

Signed-off-by: Ilan Peer &lt;ilan.peer@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: Parse station profile from association response</title>
<updated>2022-10-07T13:23:55+00:00</updated>
<author>
<name>Ilan Peer</name>
<email>ilan.peer@intel.com</email>
</author>
<published>2022-09-06T08:48:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=45ebac4f059b92906e7e86dd1a780739f883857c'/>
<id>urn:sha1:45ebac4f059b92906e7e86dd1a780739f883857c</id>
<content type='text'>
When processing an association response frame for a Multi-Link
connection, extract the per station profile for each additional
link, and use it for parsing the link elements.

As the Multi-Link element might be fragmented, add support for
reassembling a fragmented element. To simplify memory management
logic, extend 'struct ieee802_11_elems' to hold a scratch buffer,
which is used for the defragmentation. Once an element is
reconstructed in the scratch area, point the corresponding element
pointer to it. Currently only defragmentation of Multi-Link element
and the contained per-STA profile subelement is supported.

Signed-off-by: Ilan Peer &lt;ilan.peer@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: remove/avoid misleading prints</title>
<updated>2022-10-07T12:40:33+00:00</updated>
<author>
<name>James Prestwood</name>
<email>prestwoj@gmail.com</email>
</author>
<published>2022-09-15T19:55:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=092197f1f47f8359b46ea62445d87561949b577d'/>
<id>urn:sha1:092197f1f47f8359b46ea62445d87561949b577d</id>
<content type='text'>
At some point a few kernel debug prints started appearing which
indicated something was sending invalid IEs:

"bad VHT capabilities, disabling VHT"
"Invalid HE elem, Disable HE"

Turns out these were being printed because the local hardware
supported HE/VHT but the peer/AP did not. Bad/invalid indicates,
to me at least, that the IE is in some way malformed, not missing.

For the HE print (ieee80211_verify_peer_he_mcs_support) it will
now silently fail if the HE capability element is missing (still
prints if the element size is wrong).

For the VHT print, it has been removed completely and will silently
set the DISABLE_VHT flag which is consistent with how DISABLE_HT
is set.

Signed-off-by: James Prestwood &lt;prestwoj@gmail.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
</feed>
