From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: pull-request: mac80211 2018-12-19
Date: Wed, 19 Dec 2018 09:49:41 +0100 [thread overview]
Message-ID: <20181219084942.8245-1-johannes@sipsolutions.net> (raw)
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(-)
next reply other threads:[~2018-12-19 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 8:49 Johannes Berg [this message]
2018-12-19 16:35 ` pull-request: mac80211 2018-12-19 David Miller
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=20181219084942.8245-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).