All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Dmitry Vyukov <dvyukov@google.com>,
	Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: Alexander Potapenko <glider@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kasan-dev <kasan-dev@googlegroups.com>,
	Kees Cook <keescook@google.com>
Subject: Re: kasan behavior when built with unsupported compiler
Date: Tue, 7 Mar 2017 19:26:18 +0300	[thread overview]
Message-ID: <7d14c37b-54ca-05d0-9fe6-62d82ac729fa@virtuozzo.com> (raw)
In-Reply-To: <CACT4Y+Yk+7oZxuLi-X39S5bPH+NrSfLn9zySH0gYELLTE_LF5w@mail.gmail.com>



On 03/07/2017 06:54 PM, Dmitry Vyukov wrote:

> 
> Hi,
> 
> Re the message that kasan is not supported while it's still enabled in the end.
> I think it's an issue related to gcc plugins. Originally kasan was
> supported with 5.0+ thus the message. However, later we extended this
> support to 4.5+ with gcc plugins. 

You made this up, we don't have such plugin.

  parent reply	other threads:[~2017-03-07 16:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 15:35 kasan behavior when built with unsupported compiler Nikolay Borisov
2017-03-07 15:54 ` Dmitry Vyukov
2017-03-07 16:05   ` Alexander Potapenko
2017-03-07 17:33     ` Nikolay Borisov
2017-03-07 17:51       ` Alexander Potapenko
2017-03-07 20:24         ` Nikolay Borisov
2017-03-07 16:26   ` Andrey Ryabinin [this message]
2017-03-07 16:40     ` Dmitry Vyukov
2017-03-08  8:10   ` Nikolay Borisov
2017-03-08 12:34     ` Dmitry Vyukov
2017-03-09  9:46     ` Andrey Ryabinin
2017-03-09  9:47       ` Dmitry Vyukov
2017-03-09  9:58       ` Nikolay Borisov
2017-03-09 10:16         ` Dmitry Vyukov
2017-03-09 11:23           ` Andrey Ryabinin
2017-03-07 16:23 ` Andrey Ryabinin

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=7d14c37b-54ca-05d0-9fe6-62d82ac729fa@virtuozzo.com \
    --to=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.