On 1/21/2019 7:24 PM, Marc Gonzalez wrote:
On 21/01/2019 14:35, Rob Herring wrote:
On Mon, Jan 21, 2019 at 6:19 AM Robin Murphy wrote:
On 21/01/2019 11:57, Marc Gonzalez wrote:
[...]
# echo dump=0xffc021e0 > /sys/kernel/debug/kmemleak
kmemleak: Object 0xffc021e0 (size 209715
On 11/10/2018 2:58 AM, Rob Herring wrote:
On Fri, Nov 9, 2018 at 1:09 AM Prateek Patel wrote:
From: Sri Krishna chowdary
Memory reserved with "nomap" DT property in of_reserved_mem.c
removes the memory block. The removed memory blocks don't have
VA to PA mapping created
On 1/23/2019 11:24 AM, Mike Rapoport wrote:
On Tue, Jan 22, 2019 at 03:12:54PM +0100, Marc Gonzalez wrote:
On 22/01/2019 15:02, Marc Gonzalez wrote:
On 21/01/2019 18:42, Mike Rapoport wrote:
If I understood correctly, the trouble comes from no-map range allocated in
early_init_dt_alloc_res
On 1/9/2019 5:01 PM, Catalin Marinas wrote:
Hi Prateek,
On Wed, Jan 09, 2019 at 02:09:22PM +0530, Prateek Patel wrote:
From: Sri Krishna chowdary
kmemleak detects allocated objects as leaks if not accessed for
default scan time. The memory allocated using avc_alloc_node
is freed using rcu
From: Sri Krishna chowdary
Kmemleak scan can be cpu intensive and can stall user tasks at times.
To prevent this, add config DEBUG_KMEMLEAK_AUTO_SCAN to enable/disable
auto scan on boot up.
Also protect first_run with DEBUG_KMEMLEAK_AUTO_SCAN as this is meant
for only first automatic scan.
Signe
Hi Catalin,
Can you mark this patch as acknowledged so that it can be picked up by
the maintainer.
Adding Andrew.
Thanks,
On 10/29/2018 4:13 PM, Catalin Marinas wrote:
On Mon, Oct 22, 2018 at 11:38:43PM +0530, Prateek Patel wrote:
From: Sri Krishna chowdary
Kmemleak scan can be cpu
On 3/4/2019 4:04 PM, Nicolas Boichat wrote:
On Wed, Feb 13, 2019 at 4:56 PM Nicolas Boichat wrote:
On Tue, Jan 22, 2019 at 4:46 PM Prateek Patel wrote:
On 11/10/2018 2:58 AM, Rob Herring wrote:
On Fri, Nov 9, 2018 at 1:09 AM Prateek Patel wrote:
From: Sri Krishna chowdary
Memory
From: Sri Krishna chowdary
Kmemleak scan is cpu intensive and can stall user tasks at times.
To prevent this, add config DEBUG_KMEMLEAK_SCAN_ON to enable/disable
auto scan on boot up.
Also protect first_run with CONFIG_DEBUG_KMEMLEAK_SCAN_ON as this is
meant for only first automatic scan.
Signed
From: Sri Krishna chowdary
Memory reserved with "nomap" DT property in of_reserved_mem.c
removes the memory block. The removed memory blocks don't have
VA to PA mapping created in kernel page table. Kmemleak scan on
removed memory blocks is causing page faults and leading to
kernel panic. So, Dis
From: Sri Krishna chowdary
kmemleak detects allocated objects as leaks if not accessed for
default scan time. The memory allocated using avc_alloc_node
is freed using rcu mechanism when nodes are reclaimed or on
avc_flush. So, there is no real leak here and kmemleak_scan
detects it as a leak whic
10 matches
Mail list logo
