From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Andrey Ryabinin" <aryabinin@virtuozzo.com>,
"Martin Liška" <marxin@gcc.gnu.org>,
stable <stable@vger.kernel.org>, "Michal Marek" <mmarek@suse.com>,
"Alexander Potapenko" <glider@google.com>,
"open list:KERNEL BUILD + fi..." <linux-kbuild@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kasan: turn off -fsanitize-address-use-after-scope for now
Date: Wed, 23 Nov 2016 10:49:39 -0800 [thread overview]
Message-ID: <20161123104939.78f7361150020bff2bc88d2f@linux-foundation.org> (raw)
In-Reply-To: <CACT4Y+byCnW6kWUTUn+YhdJKtadhHuYn+AvvyAZ+AuToJWNufg@mail.gmail.com>
On Wed, 23 Nov 2016 10:33:41 +0100 Dmitry Vyukov <dvyukov@google.com> wrote:
> On Wed, Nov 23, 2016 at 9:46 AM, Arnd Bergmann <arnd@arndb.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@google.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@google.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.
next prev parent reply other threads:[~2016-11-23 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 22:54 Arnd Bergmann
2016-11-23 8:25 ` Andrey Ryabinin
2016-11-23 8:46 ` Arnd Bergmann
2016-11-23 9:33 ` Dmitry Vyukov
2016-11-23 18:49 ` Andrew Morton [this message]
2016-11-24 14:40 ` Dmitry Vyukov
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=20161123104939.78f7361150020bff2bc88d2f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marxin@gcc.gnu.org \
--cc=mmarek@suse.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
Powered by JetHome