linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: pull-request: mac80211 2013-12-16
Date: Mon, 16 Dec 2013 15:53:47 +0100	[thread overview]
Message-ID: <1387205627.2057.16.camel@jlt4.sipsolutions.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

John,

Two more fixes ...

Here's a fix for another potential radiotap parser buffer overrun thanks
to Evan Huus, and a fix for a cfg80211 warning in a certain corner case
(reconnecting to the same BSS).

Let me know if there's any problem.

johannes

The following changes since commit 0834ae3c3af44480834cce128b6fef83006e537f:

  mac80211: check csa wiphy flag in ibss before switching (2013-12-02 11:54:13 +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 bd02cd2549cfcdfc57cb5ce57ffc3feb94f70575:

  radiotap: fix bitmap-end-finding buffer overrun (2013-12-16 12:06:43 +0100)

----------------------------------------------------------------
Johannes Berg (1):
      radiotap: fix bitmap-end-finding buffer overrun

Ujjal Roy (1):
      cfg80211: fix WARN_ON for re-association to the expired BSS

 net/wireless/radiotap.c |  4 ++++
 net/wireless/sme.c      | 22 ++++++++++++----------
 2 files changed, 16 insertions(+), 10 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2013-12-16 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 14:53 Johannes Berg [this message]
2013-12-17 18:56 ` pull-request: mac80211 2013-12-16 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=1387205627.2057.16.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).