<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/mac80211/rx.c, branch linux-6.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-04-17T07:21:32Z</updated>
<entry>
<title>wifi: mac80211: split mesh fast tx cache into local/proxied/forwarded</title>
<updated>2024-04-17T07:21:32Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2024-04-15T12:18:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c75cdcdf869acabfdc7858827099dcde9f24e6c'/>
<id>urn:sha1:8c75cdcdf869acabfdc7858827099dcde9f24e6c</id>
<content type='text'>
Depending on the origin of the packets (and their SA), 802.11 + mesh headers
could be filled in differently. In order to properly deal with that, add a
new field to the lookup key, indicating the type (local, proxied or
forwarded). This can fix spurious packet drop issues that depend on the order
in which nodes/hosts communicate with each other.

Fixes: d5edb9ae8d56 ("wifi: mac80211: mesh fast xmit support")
Signed-off-by: Felix Fietkau &lt;nbd@nbd.name&gt;
Link: https://msgid.link/20240415121811.13391-1-nbd@nbd.name
[use sizeof_field() for key_len]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: check EHT/TTLM action frame length</title>
<updated>2024-04-08T18:11:21Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2024-03-26T20:38:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7c1c73bf84c50b641449f9811e2196cdc3ca4a1b'/>
<id>urn:sha1:7c1c73bf84c50b641449f9811e2196cdc3ca4a1b</id>
<content type='text'>
Check the EHT action frame length before accessing
the action code, if it's not present then the frame
cannot be valid.

Reported-by: syzbot+75af45a00cf13243ba39@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/r/0000000000006c06870614886611@google.com/
Fixes: 8f500fbc6c65 ("wifi: mac80211: process and save negotiated TID to Link mapping request")
Link: https://msgid.link/20240326213858.19c84f34349f.I71b439f016b28f65284bb7646fe36343b74cbc9a@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: remove gfp parameter from ieee80211_obss_color_collision_notify</title>
<updated>2024-02-12T20:07:30Z</updated>
<author>
<name>Lorenzo Bianconi</name>
</author>
<published>2024-02-08T11:01:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6f656131f6988709e3bf828c3ad992032b717c2e'/>
<id>urn:sha1:6f656131f6988709e3bf828c3ad992032b717c2e</id>
<content type='text'>
Get rid of gfp parameter from ieee80211_obss_color_collision_notify
since it is no longer used.

Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;
Reviewed-by: Jeff Johnson &lt;quic_jjohnson@quicinc.com&gt;
Acked-by: Jeff Johnson &lt;quic_jjohnson@quicinc.com&gt;
Link: https://msgid.link/f91e1c78896408ac556586ba8c99e4e389aeba02.1707389901.git.lorenzo@kernel.org
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: implement MLO multicast deduplication</title>
<updated>2024-02-08T14:00:42Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2024-01-29T19:04:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=676259100cf3a81dd2d47918b36edb237986b9df'/>
<id>urn:sha1:676259100cf3a81dd2d47918b36edb237986b9df</id>
<content type='text'>
If the vif is an MLD then it may receive multicast from
different links, and should drop those frames according
to the SN. Implement that.

Link: https://msgid.link/20240129200456.693b77d14b44.I491846f2bea0058c14eab6422962c10bfae9b675@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: add/use ieee80211_get_sn()</title>
<updated>2024-02-08T14:00:42Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2024-01-29T19:04:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b1344b1399daec9aca62bd0b2ea94874f5b8e126'/>
<id>urn:sha1:b1344b1399daec9aca62bd0b2ea94874f5b8e126</id>
<content type='text'>
This will also be useful for MLO duplicate multicast
detection, but add it already here and use it in one
place that trivially converts.

Link: https://msgid.link/20240129200456.f0ff49c80006.I850d2785ab1640e56e262d3ad7343b87f6962552@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: remove extra shadowing variable</title>
<updated>2024-02-08T11:50:12Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2024-01-31T15:49:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=efa2cce6e272b36c7f9687385ef4fd538cc3bf51'/>
<id>urn:sha1:efa2cce6e272b36c7f9687385ef4fd538cc3bf51</id>
<content type='text'>
Not sure how this happened or how nothing complained, but
this variable already exists in the outer function scope
with the same value (and the SKB isn't changed either.)
Remove the extra one.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: add support for negotiated TTLM request</title>
<updated>2024-01-26T08:39:49Z</updated>
<author>
<name>Ayala Beker</name>
</author>
<published>2024-01-02T19:35:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f7660b3f584aadd25dde18aa1902488577a15863'/>
<id>urn:sha1:f7660b3f584aadd25dde18aa1902488577a15863</id>
<content type='text'>
Update neg_ttlm and active_links according to the new mapping,
and send a negotiated TID-to-link map request with the new mapping.

Signed-off-by: Ayala Beker &lt;ayala.beker@intel.com&gt;
Reviewed-by: Gregory Greenman &lt;gregory.greenman@intel.com&gt;
Reviewed-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Miri Korenblit &lt;miriam.rachel.korenblit@intel.com&gt;
Link: https://msgid.link/20240102213313.eeb385d771df.I2a5441c14421de884dbd93d1624ce7bb2c944833@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: process and save negotiated TID to Link mapping request</title>
<updated>2024-01-26T08:39:48Z</updated>
<author>
<name>Ayala Beker</name>
</author>
<published>2024-01-02T19:35:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8f500fbc6c655976c8062b1f1e55bd0b3095d6c2'/>
<id>urn:sha1:8f500fbc6c655976c8062b1f1e55bd0b3095d6c2</id>
<content type='text'>
An MLD may send TID-to-Link mapping request frame to negotiate
TID to link mapping with a peer MLD.
Support handling negotiated TID-to-Link mapping request frame
by parsing the frame, asking the driver whether it supports the
received mapping or not, and sending a TID-to-Link mapping response
to the AP MLD.
Theoretically, links that became inactive due to the received TID-to-Link
mapping request, can be selected to be activated but this would require
tearing down the negotiated TID-to-Link mapping, which is still not
supported.

Signed-off-by: Ayala Beker &lt;ayala.beker@intel.com&gt;
Reviewed-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Reviewed-by: Gregory Greenman &lt;gregory.greenman@intel.com&gt;
Signed-off-by: Miri Korenblit &lt;miriam.rachel.korenblit@intel.com&gt;
Link: https://msgid.link/20240102213313.0bc1a24fcc9d.Ie72e47dc6f8c77d4a2f0947b775ef6367fe0edac@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: add kunit tests for public action handling</title>
<updated>2024-01-03T14:35:09Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-12-20T15:19:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0738e55c384828ccd61170e2d6f1c11196d848e6'/>
<id>urn:sha1:0738e55c384828ccd61170e2d6f1c11196d848e6</id>
<content type='text'>
Check the logic in ieee80211_drop_unencrypted_mgmt()
according to a list of test cases derived from the
spec.

Reviewed-by: Benjamin Berg &lt;benjamin.berg@intel.com&gt;
Link: https://msgid.link/20231220151952.415232-4-benjamin@sipsolutions.net
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: allow 64-bit radiotap timestamps</title>
<updated>2023-12-21T19:35:15Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-12-20T11:41:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e62c0fcc0e06a36b40615885eb86eb407ac8d0dd'/>
<id>urn:sha1:e62c0fcc0e06a36b40615885eb86eb407ac8d0dd</id>
<content type='text'>
When reporting the radiotap timestamp, the mactime field is
usually unused, we take the data from the device_timestamp.
However, there can be cases where the radiotap timestamp is
better reported as a 64-bit value, so since the mactime is
free, add a flag to support using the mactime as a 64-bit
radiotap timestamp.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Reviewed-by: Gregory Greenman &lt;gregory.greenman@intel.com&gt;
Reviewed-by: Benjamin Berg &lt;benjamin.berg@intel.com&gt;
Signed-off-by: Miri Korenblit &lt;miriam.rachel.korenblit@intel.com&gt;
Link: https://msgid.link/20231220133549.00c8b9234f0c.Ie3ce5eae33cce88fa01178e7aea94661ded1ac24@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
</feed>
