pull-request: mac80211 2018-10-04

Hi Dave,

I got three more fixes submitted, and am sending those to you
now in the hope of still getting them in, although all of the
bugs are actually older than the current cycle.

If there's a release on Sunday then I guess I won't care, but
if not then I'd appreciate if you could pull net into net-next
as I have at least one patch there that otherwise doesn't apply
(at least the result wouldn't compile). Not sure if you've seen
anything from Greg indicating either way.

Anyway, for now these fixes look good to me, so please pull or
let me know if there's any problem.

Thanks,
johannes



The following changes since commit 43955a45dc0b4f3be7f0c3afc0e080ed59bb5280:

  netlink: fix typo in nla_parse_nested() comment (2018-09-29 11:48:26 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2018-10-04

for you to fetch changes up to 1db58529454742f67ebd96e3588315e880b72837:

  cfg80211: fix use-after-free in reg_process_hint() (2018-10-01 09:14:03 +0200)

----------------------------------------------------------------
Just three small fixes:
 * fix use-after-free in regulatory code
 * fix rx-mgmt key flag in AP mode (mac80211)
 * fix wireless extensions compat code memory leak

----------------------------------------------------------------
Felix Fietkau (1):
      mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys

Stefan Seyfried (1):
      cfg80211: fix wext-compat memory leak

Yu Zhao (1):
      cfg80211: fix use-after-free in reg_process_hint()

 net/mac80211/cfg.c         |  2 +-
 net/wireless/reg.c         |  7 ++++---
 net/wireless/wext-compat.c | 14 ++++++++++----
 3 files changed, 15 insertions(+), 8 deletions(-)

From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu,  4 Oct 2018 21:43:54 +0200

> I got three more fixes submitted, and am sending those to you
> now in the hope of still getting them in, although all of the
> bugs are actually older than the current cycle.
> 
> If there's a release on Sunday then I guess I won't care, but
> if not then I'd appreciate if you could pull net into net-next
> as I have at least one patch there that otherwise doesn't apply
> (at least the result wouldn't compile). Not sure if you've seen
> anything from Greg indicating either way.
> 
> Anyway, for now these fixes look good to me, so please pull or
> let me know if there's any problem.

Pulled, thanks!