public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: stable@vger.kernel.org, Sami Tolvanen <samitolvanen@google.com>,
	Andrey Konovalov <andreyknvl@google.com>
Subject: Re: kasan patches
Date: Sat, 11 Aug 2018 18:40:35 +0200	[thread overview]
Message-ID: <20180811164035.GA14460@kroah.com> (raw)
In-Reply-To: <CAKwvOdmuV6FtKyMQOmo8OgOwnMSTe037G17xEDG-4HE4E4ViHw@mail.gmail.com>

On Mon, Aug 06, 2018 at 02:08:32PM -0700, Nick Desaulniers wrote:
> These patches are needed for kasan+clang support.  I confirmed they
> apply cleanly in order (top to bottom):
> 
> 4.9:
> commit c5caf21ab0cf8 ("kasan: turn on -fsanitize-address-use-after-scope")
> commit 0e410e158e5b ("kasan: don't emit builtin calls when sanitization is off")

By applying these, I get a ton of new build warnings, so I can't add
them :(

> 4.4:
> commit c5caf21ab0cf8 ("kasan: turn on -fsanitize-address-use-after-scope")

I'm guessing I will get build warnings here too :(

> ===
> 
> 0e410e158e5b is the one I'm interested in. Looks like it landed in
> 4.16, and got backported to 4.14-stable.
> 
> ===
> 
> c5caf21ab0cf8 depends on c6d308534aef6 ("UBSAN: run-time undefined
> behavior sanity checker"), and I don't want to bring in all of UBSAN
> to 4.4. I'll send a patch for 0e410e158e5b.

I don't undersand, can you send a patch series for the patches you want
to have applied?  That makes it easier to understand.

thanks,

greg k-h

  reply	other threads:[~2018-08-11 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 21:08 kasan patches Nick Desaulniers
2018-08-11 16:40 ` Greg KH [this message]
2018-08-13 21:25   ` Nick Desaulniers
2018-08-14  7:24     ` Greg KH
2018-08-14  7:37       ` Greg KH
2018-08-14 12:44         ` Andrey Konovalov
2018-08-14 13:51           ` Greg KH
2018-08-14 20:33           ` Nick Desaulniers
2018-08-14 20:56             ` Arnd Bergmann
2018-08-14 22:04               ` Nick Desaulniers

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=20180811164035.GA14460@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreyknvl@google.com \
    --cc=ndesaulniers@google.com \
    --cc=samitolvanen@google.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