mbox series

pull-request: mac80211 2018-12-19

Message ID 20181219084942.8245-1-johannes@sipsolutions.net (mailing list archive)
State Not Applicable
Delegated to: Kalle Valo
Headers show
Series pull-request: mac80211 2018-12-19 | expand

Pull-request

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

Message

Johannes Berg Dec. 19, 2018, 8:49 a.m. UTC
Hi Dave,

It's getting late in the cycle, so I don't know if you still want to
take these in, but we have three fixes for kernel crashes we've seen
at least here at Intel.

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

Thanks,
johannes



The following changes since commit a5f3932646a74e690ed532a1f421f75c3b8cf1ec:

  net: dsa: mv88e6xxx: set ethtool regs version (2018-12-17 23:29:00 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 34b1e0e9efe101822e83cc62d22443ed3867ae7a:

  mac80211: free skb fraglist before freeing the skb (2018-12-19 09:40:17 +0100)

----------------------------------------------------------------
Just three fixes:
 * fix a memory leak in an error path
 * fix TXQs in interface teardown
 * free fraglist if we used it internally
   before returning SKB

----------------------------------------------------------------
Johannes Berg (1):
      nl80211: fix memory leak if validate_pae_over_nl80211() fails

Sara Sharon (2):
      mac80211: fix a kernel panic when TXing after TXQ teardown
      mac80211: free skb fraglist before freeing the skb

 net/mac80211/iface.c   | 3 +++
 net/mac80211/main.c    | 2 --
 net/mac80211/status.c  | 5 +++++
 net/wireless/nl80211.c | 4 +++-
 4 files changed, 11 insertions(+), 3 deletions(-)

Comments

David Miller Dec. 19, 2018, 4:35 p.m. UTC | #1
From: Johannes Berg <johannes@sipsolutions.net>
Date: Wed, 19 Dec 2018 09:49:41 +0100

> It's getting late in the cycle, so I don't know if you still want to
> take these in, but we have three fixes for kernel crashes we've seen
> at least here at Intel.
> 
> Please pull and let me know if there's any problem.

Yes, I always want your bug fixes :-)

Pulled, thanks!