From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: pull-request: mac80211 2014-03-05
Date: Wed, 05 Mar 2014 16:20:52 +0100 [thread overview]
Message-ID: <1394032852.5275.41.camel@jlt4.sipsolutions.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
John,
We have some more fixes...
Here I have a fix from Eliad for the minimal channel width calculation
in the mac80211 code which lead to monitor mode not working at all for
drivers using that. One of my fixes is for an issue noticed by Michal,
we clear an already cleared value but do it without locking, so just
remove that. The other is for a data leak - we leak two bytes of kernel
memory out over the air in QoS NULL frames because those don't get a
sequence number assigned in the TX path.
Please let me know if there's any problem.
johannes
The following changes since commit cb664981607a6b5b3d670ad57bbda893b2528d96:
mac80211: fix association to 20/40 MHz VHT networks (2014-02-27 20:53:01 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git for-john
for you to fetch changes up to 864a6040f395464003af8dd0d8ca86fed19866d4:
mac80211: clear sequence/fragment number in QoS-null frames (2014-03-05 15:49:54 +0100)
----------------------------------------------------------------
Eliad Peller (1):
mac80211: consider virtual mon when calculating min_def
Johannes Berg (2):
cfg80211: remove racy beacon_interval assignment
mac80211: clear sequence/fragment number in QoS-null frames
net/mac80211/chan.c | 6 ++++++
net/mac80211/mesh_ps.c | 1 +
net/mac80211/sta_info.c | 1 +
net/wireless/core.c | 2 --
4 files changed, 8 insertions(+), 2 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2014-03-05 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 15:20 Johannes Berg [this message]
2014-03-06 18:47 ` pull-request: mac80211 2014-03-05 John W. Linville
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=1394032852.5275.41.camel@jlt4.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).