LKML Archive on
help / color / mirror / Atom feed
From: Steven Rostedt <>
To: Sasha Levin <>
Cc: LKML <>,,,,,
Subject: Re: [PATCH] mm: kill kmemcheck
Date: Wed, 11 Mar 2015 10:52:10 -0400	[thread overview]
Message-ID: <20150311105210.1855c95e@gandalf.local.home> (raw)
In-Reply-To: <>

On Wed, 11 Mar 2015 10:43:29 -0400
Sasha Levin <> wrote:

> On 03/11/2015 10:26 AM, Steven Rostedt wrote:
> >> There's no real hurry to kill kmemcheck right now, but we do want to stop
> >> > supporting that in favour of KASan.
> > Understood, but the kernel is suppose to support older compilers.
> > Perhaps we can keep kmemcheck for now and say it's obsoleted if you
> > have a newer compiler. Because it will be a while before I upgrade my
> > compilers. I don't upgrade unless I have a good reason to do so. Not
> > sure KASan fulfills that requirement.
> It's not that there's a performance overhead with kmemcheck, it's the
> maintenance effort that we want to get rid of.

I totally understand this.

> The kernel should keep supporting old kernels, and after this kmemcheck
> removal your kernel will still keep working - this is more of a removal
> of a mostly unused feature that had hooks everywhere in the kernel.
> Did you actually find anything recently with kmemcheck?

I have to look. I think I did find something last year. I run it every
other month or so, so it's not something I do every day.

> How do you deal
> with the 1 CPU limit and the massive performance hit?

I just deal with it :-)

I have test boxes that I kick off and just let run. It's not that bad
if you are not using the box for actual work.

> Could you try KASan for your use case and see if it potentially uncovers
> anything new?

The problem is, I don't have a setup to build with the latest compiler.

I could build with my host compiler (that happens to be 4.9.2), but it
would take a while to build, and is not part of my work flow.

4.9.2 is very new, I think it's a bit premature to declare that the
only way to test memory allocations is with the latest and greatest

But if kmemcheck really doesn't work anymore, than perhaps we should
get rid of it.

-- Steve

  reply	other threads:[~2015-03-11 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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 [this message]
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
     [not found] ` <>
     [not found]   ` <>
2015-03-12 18:11     ` David Miller

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150311105210.1855c95e@gandalf.local.home \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] mm: kill kmemcheck' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).