lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <50DEA41E.6010409@01019freenet.de> Date: Sat, 29 Dec 2012 09:04:46 +0100 From: Andreas Hartmann <andihartmann@...19freenet.de> To: Ben Hutchings <ben@...adent.org.uk> CC: linux-kernel@...r.kernel.org, stable@...r.kernel.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, Andreas Hartmann <andihartmann@...19freenet.de>, Helmut Schaa <helmut.schaa@...glemail.com>, "John W. Linville" <linville@...driver.com>, Stanislaw Gruszka <sgruszka@...hat.com> Subject: Re: [ 104/173] rt2x00: Dont let mac80211 send a BAR when an AMPDU subframe fails Ben Hutchings wrote: > 3.2-stable review patch. If anyone has any objections, please let me know. > > ------------------ > > From: Andreas Hartmann <andihartmann@...19freenet.de> > > commit be03d4a45c09ee5100d3aaaedd087f19bc20d01f upstream. [...] This patch is a workaround for mac80211: retry sending failed BAR frames later instead of tearing down aggr (http://www.spinics.net/lists/linux-wireless/msg76379.html - f0425beda4d404a6e751439b562100b902ba9c98) See: http://thread.gmane.org/gmane.linux.kernel.wireless.general/83297/focus=83304 Meanwhile there was a bug report complaining about problems with be03d4a45 when used as STA: http://thread.gmane.org/gmane.linux.drivers.rt2x00.user/1257 You can find there a few other workaround proposals. Stanislaw Gruszka proposed here a final(?) workaround, which refines workaround be03d4a45c by shrinking it to AP function: http://thread.gmane.org/gmane.linux.kernel.wireless.general/100793 carl9170 had the same problem with f0425beda. There it was fixed like this: http://thread.gmane.org/gmane.linux.kernel.wireless.general/100793/focus=1405 This approach fixes the real problem (no aggregation handling by the firmware / hardware) by implementing it into the driver. Unfortunately, I didn't see any implementation of c9122c0d63a50 for rt2x00 until now. Kind regards, Andreas Hartmann -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists