linux-kernel - Re: KASAN+netlink, was: [PATCH] [net-next?] hns: avoid stack overflow with CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1486556665.24745.6.camel@sipsolutions.net>
Date:   Wed, 08 Feb 2017 13:24:25 +0100
From:   Johannes Berg <johannes@...solutions.net>
To:     Arnd Bergmann <arnd@...db.de>, David Miller <davem@...emloft.net>,
        netdev@...r.kernel.org
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org,
        Andrey Ryabinin <a.ryabinin@...sung.com>,
        nikolay@...ulusnetworks.com, nicolas.dichtel@...nd.com,
        adobriyan@...il.com,
        linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: KASAN+netlink, was: [PATCH] [net-next?] hns: avoid stack
 overflow with CONFIG_KASAN

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