mbox series

pull-request: mac80211 2019-11-08

Message ID 20191108123850.17527-1-johannes@sipsolutions.net (mailing list archive)
State Not Applicable
Headers show
Series pull-request: mac80211 2019-11-08 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-net-2019-11-08

Message

Johannes Berg Nov. 8, 2019, 12:38 p.m. UTC
Hi Dave,

Three more small fixes for the current cycle - the allocation
and its failure must've been around for a while but we've started
hitting it (I'm also investigating if we have a leak), and the
inactive time thing also must've been around forever.

Please pull and let me know if there's any problem.

Thanks,
johannes



The following changes since commit e0a312629fefa943534fc46f7bfbe6de3fdaf463:

  ipv4: Fix table id reference in fib_sync_down_addr (2019-11-07 16:14:36 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-net-2019-11-08

for you to fetch changes up to 285531f9e6774e3be71da6673d475ff1a088d675:

  mac80211: fix station inactive_time shortly after boot (2019-11-08 09:17:28 +0100)

----------------------------------------------------------------
Three small fixes:
 * we hit a failure path bug related to
   ieee80211_txq_setup_flows()
 * also use kvmalloc() to make that less likely
 * fix a timing value shortly after boot (during
   INITIAL_JIFFIES)

----------------------------------------------------------------
Ahmed Zaki (1):
      mac80211: fix station inactive_time shortly after boot

Johannes Berg (1):
      mac80211: fix ieee80211_txq_setup_flows() failure path

Toke Høiland-Jørgensen (1):
      net/fq_impl: Switch to kvmalloc() for memory allocation

 include/net/fq_impl.h   | 4 ++--
 net/mac80211/main.c     | 2 +-
 net/mac80211/sta_info.c | 3 ++-
 3 files changed, 5 insertions(+), 4 deletions(-)

Comments

David Miller Nov. 8, 2019, 7:37 p.m. UTC | #1
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri,  8 Nov 2019 13:38:49 +0100

> Three more small fixes for the current cycle - the allocation
> and its failure must've been around for a while but we've started
> hitting it (I'm also investigating if we have a leak), and the
> inactive time thing also must've been around forever.
> 
> Please pull and let me know if there's any problem.

Ok, also pulled, thanks.