From: Johannes Berg <johannes@sipsolutions.net>
To: Arnd Bergmann <arnd@arndb.de>, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrey Ryabinin <a.ryabinin@samsung.com>,
nikolay@cumulusnetworks.com, nicolas.dichtel@6wind.com,
adobriyan@gmail.com,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: KASAN+netlink, was: [PATCH] [net-next?] hns: avoid stack overflow with CONFIG_KASAN
Date: Wed, 08 Feb 2017 13:24:25 +0100 [thread overview]
Message-ID: <1486556665.24745.6.camel@sipsolutions.net> (raw)
In-Reply-To: <4910112.l20yySyWnA@wuerfel> (sfid-20170208_130733_449950_64BEF84C)
On Wed, 2017-02-08 at 13:03 +0100, Arnd Bergmann wrote:
>
> - Moving nla_put_{u8,u16,u32} out of line is probably uncontroversial
> and
> it helps enough with br_netlink.c, but nl820211 is worse and needs
> some
> additional fiddling.
Why would that not be sufficient by itself for nl80211?
Btw, what's causing this to start with? Can't the compiler reuse the
stack places?
johannes
next prev parent reply other threads:[~2017-02-08 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 16:35 [PATCH] [net-next?] hns: avoid stack overflow with CONFIG_KASAN Arnd Bergmann
2017-02-06 17:03 ` David Miller
2017-02-08 12:03 ` KASAN+netlink, was: " Arnd Bergmann
2017-02-08 12:24 ` Johannes Berg [this message]
2017-02-08 13:10 ` Arnd Bergmann
2017-02-08 14:58 ` Andrey Ryabinin
2017-02-08 16:00 ` David Laight
2017-02-08 16:27 ` 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=1486556665.24745.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=a.ryabinin@samsung.com \
--cc=adobriyan@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=nikolay@cumulusnetworks.com \
--cc=stable@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).