From: Steven Rostedt <rostedt@goodmis.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Wed, 11 Mar 2015 08:40:34 -0400 [thread overview]
Message-ID: <20150311084034.04ce6801@grimm.local.home> (raw)
In-Reply-To: <55003666.3020100@oracle.com>
On Wed, 11 Mar 2015 08:34:46 -0400
Sasha Levin <sasha.levin@oracle.com> wrote:
> Fair enough. We knew there are existing kmemcheck users, but KASan should be
> superior both in performance and the scope of bugs it finds. It also shouldn't
> impose new limitations beyond requiring gcc 4.9.2+.
>
Ouch! OK, then I can't use it. I'm currently compiling with gcc 4.6.3.
It will be a while before I upgrade my build farm to something newer.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Wed, 11 Mar 2015 08:40:34 -0400 [thread overview]
Message-ID: <20150311084034.04ce6801@grimm.local.home> (raw)
In-Reply-To: <55003666.3020100@oracle.com>
On Wed, 11 Mar 2015 08:34:46 -0400
Sasha Levin <sasha.levin@oracle.com> wrote:
> Fair enough. We knew there are existing kmemcheck users, but KASan should be
> superior both in performance and the scope of bugs it finds. It also shouldn't
> impose new limitations beyond requiring gcc 4.9.2+.
>
Ouch! OK, then I can't use it. I'm currently compiling with gcc 4.6.3.
It will be a while before I upgrade my build farm to something newer.
-- Steve
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-03-11 12:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:43 [PATCH] mm: kill kmemcheck Sasha Levin
2015-03-11 11:43 ` Sasha Levin
2015-03-11 11:43 ` Sasha Levin
2015-03-11 12:19 ` Steven Rostedt
2015-03-11 12:19 ` Steven Rostedt
2015-03-11 12:34 ` Sasha Levin
2015-03-11 12:34 ` Sasha Levin
2015-03-11 12:40 ` Steven Rostedt [this message]
2015-03-11 12:40 ` Steven Rostedt
2015-03-11 13:39 ` Sasha Levin
2015-03-11 13:39 ` Sasha Levin
2015-03-11 14:23 ` Dave Jones
2015-03-11 14:23 ` Dave Jones
2015-03-11 14:26 ` Steven Rostedt
2015-03-11 14:26 ` Steven Rostedt
2015-03-11 14:43 ` Sasha Levin
2015-03-11 14:43 ` Sasha Levin
2015-03-11 14:52 ` Steven Rostedt
2015-03-11 14:52 ` Steven Rostedt
2015-03-17 1:48 ` Sasha Levin
2015-03-17 1:48 ` Sasha Levin
2015-03-17 2:33 ` Steven Rostedt
2015-03-17 2:33 ` Steven Rostedt
2015-03-11 14:35 ` Boaz Harrosh
2015-03-11 14:35 ` Boaz Harrosh
2015-03-11 17:20 ` David Miller
2015-03-11 17:20 ` David Miller
2015-03-11 17:25 ` Sasha Levin
2015-03-11 17:25 ` Sasha Levin
2015-03-11 18:44 ` David Miller
2015-03-11 18:44 ` David Miller
2015-03-11 20:01 ` Andrey Ryabinin
2015-03-11 20:01 ` Andrey Ryabinin
2015-03-11 20:48 ` David Miller
2015-03-11 20:48 ` David Miller
2015-03-12 0:57 ` Rusty Russell
2015-03-12 0:57 ` Rusty Russell
2015-03-12 0:57 ` Rusty Russell
2015-03-12 3:49 ` Michael Ellerman
2015-03-12 3:49 ` Michael Ellerman
2015-03-12 3:49 ` Michael Ellerman
2015-03-12 12:40 ` Sasha Levin
2015-03-12 12:40 ` Sasha Levin
2015-03-12 18:11 ` David Miller
2015-03-12 13:47 ` Steven Rostedt
2015-03-12 13:47 ` Steven Rostedt
2015-03-12 13:47 ` Steven Rostedt
2015-03-12 7:07 ` Pekka Enberg
2015-03-12 7:07 ` Pekka Enberg
2015-03-12 12:51 ` Sasha Levin
2015-03-12 12:51 ` Sasha Levin
2015-03-12 13:00 ` Jonathan Corbet
2015-03-12 13:00 ` Jonathan Corbet
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=20150311084034.04ce6801@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.levin@oracle.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.