linux-kernel - Re: [PATCH] kasan: turn off -fsanitize-address-use-after-scope for now

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] [day] [month] [year] [list]

Message-ID: <CACT4Y+YXQC7fHn_P-nPC1rj4toKoZCziPz2s_KkMmEPzgxjz4w@mail.gmail.com>
Date:   Thu, 24 Nov 2016 15:40:00 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Martin Liška <marxin@....gnu.org>,
        stable <stable@...r.kernel.org>, Michal Marek <mmarek@...e.com>,
        Alexander Potapenko <glider@...gle.com>,
        "open list:KERNEL BUILD + fi..." <linux-kbuild@...r.kernel.org>,
        kasan-dev <kasan-dev@...glegroups.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kasan: turn off -fsanitize-address-use-after-scope for now

On Wed, Nov 23, 2016 at 7:49 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Wed, 23 Nov 2016 10:33:41 +0100 Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
>> On Wed, Nov 23, 2016 at 9:46 AM, Arnd Bergmann <arnd@...db.de> wrote:
>> > On Wednesday, November 23, 2016 11:25:49 AM CET Andrey Ryabinin wrote:
>> >>
>> >> We have implementation for this feature:
>> >>         "[PATCH] kasan: support use-after-scope detection" - http://lkml.kernel.org/r/<1479226045-145148-1-git-send-email-dvyukov@...gle.com>
>> >> and given how simple it is I'd suggest to just backport implementation.
>> >>
>> >> BTW, we also need "[PATCH] kasan: update kasan_global for gcc 7" - http://lkml.kernel.org/r/<1479219743-28682-1-git-send-email-dvyukov@...gle.com>
>> >> in v4.0+ stable.
>> >
>> > Ah, good. What's the plan for this patch? Would you still expect to
>> > see that merged into v4.9, or get backported later once it's part of v4.10?
>> >
>> > Either way, you proabably want a Cc:stable tag on it to trigger the
>> > backport to older kernels.
>>
>> +Andrew, what is the plan for the "[PATCH] kasan: update kasan_global
>> for gcc 7" patch?
>> Do I need to remail to include Cc:stable?
>
> I'm planning on merging it into 4.10-rc1.  There's nothing in the
> changelog to indicate that it is more urgent than that.
>
> Please send out a new changelog which can be used to justify a merge
> into 4.9 and -stable.

Remailed the patches with Cc: stable@...r.kernel.org # 4.0+
and with a note that without these patches KASAN is broken with gcc 7.