Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1694756

Re: [PATCH v2] kmemleak: add oom=<disable|ignore> runtime parameter

From Catalin Marinas <catalin.marinas@arm.com>
Newsgroups linux.kernel
Subject Re: [PATCH v2] kmemleak: add oom=<disable|ignore> runtime parameter
Date 2017-07-24 16:10 +0200
Message-ID <u6MdB-5Wc-33@gated-at.bofh.it> (permalink)
References <u6HGX-2Pd-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Jul 24, 2017 at 05:16:34PM +0800, shuwang@redhat.com wrote:
> When running memory stress tests, kmemleak could be easily disabled in
> function create_object as system is out of memory and kmemleak failed to
> alloc from object_cache. Since there's no way to enable kmemleak after
> it's off, simply ignore the object_cache alloc failure will just loses
> track of some memory objects, but could increase the usability of kmemleak
> under memory stress.

I wonder how usable kmemleak is when not recording all the allocated
objects. If some of these memory blocks contain references to others,
such referenced objects could be reported as leaks (basically increasing
the false positives rate).

-- 
Catalin

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

[PATCH v2] kmemleak: add oom=<disable|ignore> runtime parameter shuwang@redhat.com - 2017-07-24 11:20 +0200
  Re: [PATCH v2] kmemleak: add oom=<disable|ignore> runtime parameter Catalin Marinas <catalin.marinas@arm.com> - 2017-07-24 16:10 +0200

csiph-web