From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] fix mac80211 crypto races
Date: Wed, 06 Jul 2011 12:09:29 +0200 [thread overview]
Message-ID: <20110706100929.554431961@sipsolutions.net> (raw)
mac80211's crypto code is racing against itself, since
we can process multiple TX packets at the same time on
different ACs.
These two patches fix this. I'm not backporting them
since nobody complained, and the worst case probably
is lost packets (though in the case of TKIP maybe it
can cause countermeasures?)
johannes
next reply other threads:[~2011-07-06 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 10:09 Johannes Berg [this message]
2011-07-06 10:09 ` [PATCH 1/2] mac80211: fix TKIP races, make API easier to use Johannes Berg
2011-07-07 20:28 ` [PATCH 1/2 v2] " Johannes Berg
2011-07-06 10:09 ` [PATCH 2/2] mac80211: fix CCMP PN race Johannes Berg
2011-07-06 19:28 ` Johannes Berg
2011-07-06 19:59 ` [PATCH 2/2 v2] mac80211: fix CCMP races Johannes Berg
2011-07-06 20:00 ` [PATCH 3/2] mac80211: fix CMAC races Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110706100929.554431961@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).