mt76x0: mark 802.11w as supported
PATCH 1/1 mt76x0: mark 802.11w as supported
commit 0ae976a11b4fb5704b597e103b5189237641c1a1 upstream.
This is one line hw feature backport from 0ae976a11b4f ("mt76x0: init hw capabilities"), which add also other different features, however those are not supported in 4.19.
802.11w is supported by mac80211 and mt76x0u driver in 4.19 correctly fall-back to software encryption when 802.11w ciphers are used.
Without the patch we fail to associate with WPA3 APs, so this is considered as fix.
--- drivers/net/wireless/mediatek/mt76/mt76x0/init.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/wireless/mediatek/mt76/mt76x0/init.c +1 -0
@@ -681,6 +681,7 @@ int mt76x0_register_device(struct mt76x0_dev *dev)ieee80211_hw_set (hw,SUPPORTS_HT_CCK_RATES );ieee80211_hw_set (hw,AMPDU_AGGREGATION );ieee80211_hw_set (hw,SUPPORTS_RC_TABLE ); +ieee80211_hw_set (hw,MFP_CAPABLE ); hw->max_rates =1 ; hw->max_report_rates =7 ; hw->max_rate_tries =1 ;
Signature · 1 line
2.7.5
Greg KH
maintainerQuoted 12 lines · Stanislaw Gruszka
commit
0ae976a11b4fb5704b597e103b5189237641c1a1upstream.This is one line hw feature backport from
0ae976a11b4f("mt76x0: init hw capabilities"), which add also other different features, however those are not supported in 4.19.802.11w is supported by mac80211 and mt76x0u driver in 4.19 correctly fall-back to software encryption when 802.11w ciphers are used.
Without the patch we fail to associate with WPA3 APs, so this is considered as fix.
Quoted 7 lines
Signed-off-by Lorenzo Bianconi <[email protected]>Signed-off-by Felix Fietkau <[email protected]>[remove marking non-working features on 4.19, make topic correspond the change]Signed-off-by Stanislaw Gruszka <[email protected]>--- drivers/net/wireless/mediatek/mt76/mt76x0/init.c | 1 + 1 file changed, 1 insertion(+)
What bug is this fixing? This never worked before, so this feels like it is adding a new feature.
thanks,
greg k-h
Quoted 21 lines · Greg KH
Quoted 12 lines · Stanislaw Gruszka
commit
0ae976a11b4fb5704b597e103b5189237641c1a1upstream.This is one line hw feature backport from
0ae976a11b4f("mt76x0: init hw capabilities"), which add also other different features, however those are not supported in 4.19.802.11w is supported by mac80211 and mt76x0u driver in 4.19 correctly fall-back to software encryption when 802.11w ciphers are used.
Without the patch we fail to associate with WPA3 APs, so this is considered as fix.
Quoted 7 lines
Signed-off-by Lorenzo Bianconi <[email protected]>Signed-off-by Felix Fietkau <[email protected]>[remove marking non-working features on 4.19, make topic correspond the change]Signed-off-by Stanislaw Gruszka <[email protected]>--- drivers/net/wireless/mediatek/mt76/mt76x0/init.c | 1 + 1 file changed, 1 insertion(+)
Quoted 2 lines
What bug is this fixing? This never worked before, so this feels like it is adding a new feature.
It's never worked before, true. It fixes problem with associating with WPA3 Access Points. Perhaps Sid (already in CC) who requested this, could justify it better.
Thanks
Stanislaw
Quoted 22 lines · Greg KH
Quoted 12 lines · Stanislaw Gruszka
commit
0ae976a11b4fb5704b597e103b5189237641c1a1upstream.This is one line hw feature backport from
0ae976a11b4f("mt76x0: init hw capabilities"), which add also other different features, however those are not supported in 4.19.802.11w is supported by mac80211 and mt76x0u driver in 4.19 correctly fall-back to software encryption when 802.11w ciphers are used.
Without the patch we fail to associate with WPA3 APs, so this is considered as fix.
Quoted 7 lines
Signed-off-by Lorenzo Bianconi <[email protected]>Signed-off-by Felix Fietkau <[email protected]>[remove marking non-working features on 4.19, make topic correspond the change]Signed-off-by Stanislaw Gruszka <[email protected]>--- drivers/net/wireless/mediatek/mt76/mt76x0/init.c | 1 + 1 file changed, 1 insertion(+)
Quoted 2 lines
What bug is this fixing? This never worked before, so this feels like it is adding a new feature.
It is easy to see how this walks the line between "new feature" and "bug". From a user's perspective, it presents obviously as a bug:
wlan0: WPA: Failed to configure IGTK to the driver
wlan0: RSN: Failed to configure IGTK
When I cannot connect to an AP and wpa_supplicant is throwing failures, it sure feels like a bug. The line for acceptance shouldn't be "never worked before" or only regressions would be fixed in stable. Instead the line should be closer to "this doesn't work and was expected to work". In 4.19.5 a patch was merged to fix monitor mode on this driver, which is a far less critical bug than not supporting 802.11w and WPA3. For me I would define "bug" as unexpected failure, and no where in the wpa_supplicant output does it say this is unsupported, instead it just plain fails, and failure is a bug.
Again, I agree that it can be seen both ways, but I'm arguing that it's a bug.
Thanks,
Zero
Quoted 4 lines
thanks,
greg k-h