From: John Crispin <john@phrozen.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, John Crispin <john@phrozen.org>
Subject: [PATCH 0/7] iw: various bug fixes
Date: Fri, 17 May 2019 21:29:49 +0200 [thread overview]
Message-ID: <20190517192956.18372-1-john@phrozen.org> (raw)
These fixes were extracted from the latest Intel/UGW. I am assuming they
ran static code analyses/Klocwork in the source.
John Crispin (7):
iw: fix memory leak inside register_mgmt_frame
iw: fix endless loop inside handle_mgmt_dump
iw: fix memory leak inside handle_cac
iw: fix fd leak inside handle_netns
iw: fix memory leak inside parse_sched_scan
iw: fix memory leaks inside handle_scan
iw: fix fp handling inside handle_vendor
mgmt.c | 4 ++++
phy.c | 25 ++++++++++++++++++-------
scan.c | 34 +++++++++++++++++-----------------
vendor.c | 5 ++++-
4 files changed, 43 insertions(+), 25 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-17 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 19:29 John Crispin [this message]
2019-05-17 19:29 ` [PATCH 1/7] iw: fix memory leak inside register_mgmt_frame John Crispin
2019-05-17 19:29 ` [PATCH 2/7] iw: fix endless loop inside handle_mgmt_dump John Crispin
2019-05-17 19:29 ` [PATCH 3/7] iw: fix memory leak inside handle_cac John Crispin
2019-05-17 19:29 ` [PATCH 4/7] iw: fix fd leak inside handle_netns John Crispin
2019-05-17 19:29 ` [PATCH 5/7] iw: fix memory leak inside parse_sched_scan John Crispin
2019-05-17 19:29 ` [PATCH 6/7] iw: fix memory leaks inside handle_scan John Crispin
2019-05-17 19:29 ` [PATCH 7/7] iw: fix fp handling inside handle_vendor John Crispin
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=20190517192956.18372-1-john@phrozen.org \
--to=john@phrozen.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).