From: Sasha Levin <sasha.levin@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
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:34:46 -0400 [thread overview]
Message-ID: <55003666.3020100@oracle.com> (raw)
In-Reply-To: <20150311081909.552e2052@grimm.local.home>
On 03/11/2015 08:19 AM, Steven Rostedt wrote:
> I removed the Cc list as it was so large, I'm sure that it exceeded the
> LKML Cc size limit, and your email probably didn't make it to the list
> (or any of them).
Thanks. I'll resend in a bit if it doesn't show up on lkml.org.
> On Wed, 11 Mar 2015 07:43:59 -0400
> Sasha Levin <sasha.levin@oracle.com> 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).
> I use kmemcheck and I am unaware of KASan. I'll try to play with KASan
> and see if it suites my needs.
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+.
Thanks,
Sasha
next prev parent reply other threads:[~2015-03-11 12:34 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 [this message]
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
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=55003666.3020100@oracle.com \
--to=sasha.levin@oracle.com \
--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=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).