netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	SUPERH <linux-sh@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Jianyu Zhan <nasa4836@gmail.com>,
	Paul Mackerras <paulus@samba.org>, Pavel Machek <pavel@ucw.cz>,
	Miklos Szeredi <mszeredi@suse.cz>,
	Christoph Lameter <cl@linux.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	"open list:GENERIC INCLUDE/A..." <linux-arch@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	Russell King <linux@arm.linux.org.uk>,
	Jingoo Han <jg1.han@samsung.com>,
	James Morris <jmorris@namei.org>,
	Chris Bainbridge <chris.bainbridge@gmail.com>,
	Antti Palosaari <crope@iki.fi>, Mel Gorman <mgorman@suse.de>,
	Ritesh Harjani <ritesh.harjani@gmail.com>,
	Shaohua Li <shli@kernel.org>,
	Alexander Duyck <alexander.h.duyck@intel.com>,
	Wang Nan <wangnan0@huawei.com>,
	Jiri
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Thu, 12 Mar 2015 08:40:22 -0400	[thread overview]
Message-ID: <55018936.5080805@oracle.com> (raw)
In-Reply-To: <1426132192.25936.7.camel@ellerman.id.au>

On 03/11/2015 11:49 PM, Michael Ellerman wrote:
> On Wed, 2015-03-11 at 07:43 -0400, Sasha Levin wrote:
>> As discussed on LSF/MM, kill kmemcheck.
>>
>> KASan is a replacement that is able to work without the limitation of
>> kmemcheck (single CPU, slow). KASan is already upstream.
>>
>> We are also not aware of any users of kmemcheck (or users who don't consider
>> KASan as a suitable replacement).
> 
> From Documentation/kasan.txt:
> 
>     therefore you will need a certain version of GCC > 4.9.2
> 
> AFAIK gcc 4.9.3 hasn't been released yet. (Or does it mean >= 4.9.2 ?)
> 
> Can we perhaps wait until there is a released version of GCC that supports
> KASan? And maybe then a touch longer so folks can test it works on their
> platforms?

I think this is just an off-by-one in the documentation. The cover letter for
the KASan patchset stated:

	KASAN uses compile-time instrumentation for checking every memory access, therefore you
	will need a fresh GCC >= v4.9.2


Thanks,
Sasha

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2015-03-12 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 11:43 [PATCH] mm: kill kmemcheck Sasha Levin
2015-03-11 12:19 ` Steven Rostedt
2015-03-11 12:34   ` Sasha Levin
2015-03-11 12:40     ` Steven Rostedt
2015-03-11 13:39       ` Sasha Levin
2015-03-11 14:23         ` Dave Jones
2015-03-11 14:26         ` Steven Rostedt
2015-03-11 14:43           ` Sasha Levin
2015-03-11 14:52             ` Steven Rostedt
2015-03-17  1:48               ` Sasha Levin
2015-03-17  2:33                 ` Steven Rostedt
2015-03-11 14:35         ` Boaz Harrosh
2015-03-11 17:20         ` David Miller
2015-03-11 17:25           ` Sasha Levin
2015-03-11 18:44             ` David Miller
2015-03-11 20:01               ` Andrey Ryabinin
2015-03-11 20:48                 ` David Miller
2015-03-12  0:57 ` Rusty Russell
2015-03-12  3:49 ` Michael Ellerman
2015-03-12 12:40   ` Sasha Levin [this message]
2015-03-12 13:47   ` Steven Rostedt
2015-03-12  7:07 ` Pekka Enberg
2015-03-12 12:51   ` Sasha Levin
2015-03-12 13:00   ` Jonathan Corbet

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=55018936.5080805@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=chris.bainbridge@gmail.com \
    --cc=cl@linux.com \
    --cc=crope@iki.fi \
    --cc=geert+renesas@glider.be \
    --cc=jg1.han@samsung.com \
    --cc=jmorris@namei.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=mgorman@suse.de \
    --cc=mpe@ellerman.id.au \
    --cc=mszeredi@suse.cz \
    --cc=nasa4836@gmail.com \
    --cc=paulus@samba.org \
    --cc=pavel@ucw.cz \
    --cc=ritesh.harjani@gmail.com \
    --cc=shli@kernel.org \
    --cc=vdavydov@parallels.com \
    --cc=wangnan0@huawei.com \
    --cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).