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 2017-10-09
Date: Mon, 9 Oct 2017 09:40:12 +0200 [thread overview]
Message-ID: <20171009074013.1979-1-johannes@sipsolutions.net> (raw)
Hi Dave,
The QCA folks found another netlink problem - we were missing validation
of some attributes. It's not super problematic since one can only read a
few bytes beyond the message (and that memory must exist), but here's the
fix for it.
I thought perhaps we can make nla_parse_nested() require a policy, but
given the two-stage validation/parsing in regular netlink that won't work.
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit 9f775ead5e570e7e19015b9e4e2f3dd6e71a5935:
l2tp: fix l2tp_eth module loading (2017-10-01 22:35:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2017-10-09
for you to fetch changes up to ad670233c9e1d5feb365d870e30083ef1b889177:
nl80211: Define policy for packet pattern attributes (2017-10-04 14:39:21 +0200)
----------------------------------------------------------------
Just a single fix for a missing netlink attribute validation.
----------------------------------------------------------------
Peng Xu (1):
nl80211: Define policy for packet pattern attributes
net/wireless/nl80211.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
next reply other threads:[~2017-10-09 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 7:40 Johannes Berg [this message]
2017-10-09 16:53 ` pull-request: mac80211 2017-10-09 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=20171009074013.1979-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