From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with SMTP id B81F06B005D for ; Fri, 26 Jun 2009 04:47:54 -0400 (EDT) Date: Fri, 26 Jun 2009 11:50:56 +0300 From: Sergey Senozhatsky Subject: Re: kmemleak suggestion (long message) Message-ID: <20090626085056.GC3451@localdomain.by> References: <20090625221816.GA3480@localdomain.by> <20090626065923.GA14078@elte.hu> <84144f020906260007u3e79086bv91900e487ba0fb50@mail.gmail.com> <20090626081452.GB3451@localdomain.by> <1246004270.27533.16.camel@penberg-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1246004270.27533.16.camel@penberg-laptop> Sender: owner-linux-mm@kvack.org To: Pekka Enberg Cc: Ingo Molnar , Catalin Marinas , "Paul E. McKenney" , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On (06/26/09 11:17), Pekka Enberg wrote: > Well, the thing is, I am not sure it's needed if we implement Ingo's > suggestion. After all, syslog is no longer spammed very hard and you can > do all the filtering in userspace when you read /debug/mm/kmemleak file, > no? > > Pekka > Well, we just move 'spam' out of syslog. Not dealing with 'spam' itself. I'm not sure about 'filtering in userspace when you read'. Suppose I use 'tail -f /debug/mm/kmemleak'. How can I easy suppress printing of (for example): [ 64.494396] kmemleak: unreferenced object 0xf63fee18 (size 32): [ 64.494400] kmemleak: comm "init", pid 1, jiffies 4294879195 [ 64.494402] kmemleak: backtrace: [ 64.494408] kmemleak: [] kmemleak_alloc+0x11b/0x2b0 [ 64.494412] kmemleak: [] kmem_cache_alloc+0x111/0x1c0 [ 64.494418] kmemleak: [] tty_ldisc_try_get+0x2b/0x130 [ 64.494422] kmemleak: [] tty_ldisc_get+0x37/0x70 [ 64.494426] kmemleak: [] tty_ldisc_reinit+0x34/0x70 [ 64.494431] kmemleak: [] tty_ldisc_release+0x35/0x60 [ 64.494435] kmemleak: [] tty_release_dev+0x33e/0x500 [ 64.494439] kmemleak: [] tty_release+0x20/0x40 [ 64.494443] kmemleak: [] __fput+0xed/0x200 [ 64.494446] kmemleak: [] fput+0x22/0x40 [ 64.494450] kmemleak: [] filp_close+0x49/0x90 [ 64.494454] kmemleak: [] sys_close+0x68/0xc0 [ 64.494459] kmemleak: [] sysenter_do_call+0x12/0x22 [ 64.494467] kmemleak: [] 0xffffffff Or any report with tty_ldisc_try_get (ppp generates tons of them). echo "block=c12cf49b" > /sys/.../kmemleak looks good to me. Sergey -- 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: email@kvack.org