Re: kmemleak suggestion (long message)

[Sergey Senozhatsky]

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:     [<c10e92fb>] kmemleak_alloc+0x11b/0x2b0
[   64.494412] kmemleak:     [<c10e4b91>] kmem_cache_alloc+0x111/0x1c0
[   64.494418] kmemleak:     [<c12cf49b>] tty_ldisc_try_get+0x2b/0x130
[   64.494422] kmemleak:     [<c12cf7d7>] tty_ldisc_get+0x37/0x70
[   64.494426] kmemleak:     [<c12cfa54>] tty_ldisc_reinit+0x34/0x70
[   64.494431] kmemleak:     [<c12cfac5>] tty_ldisc_release+0x35/0x60
[   64.494435] kmemleak:     [<c12ca1fe>] tty_release_dev+0x33e/0x500
[   64.494439] kmemleak:     [<c12ca3e0>] tty_release+0x20/0x40
[   64.494443] kmemleak:     [<c10ed5fd>] __fput+0xed/0x200
[   64.494446] kmemleak:     [<c10ed732>] fput+0x22/0x40
[   64.494450] kmemleak:     [<c10e96a9>] filp_close+0x49/0x90
[   64.494454] kmemleak:     [<c10e9758>] sys_close+0x68/0xc0
[   64.494459] kmemleak:     [<c100324b>] sysenter_do_call+0x12/0x22
[   64.494467] kmemleak:     [<ffffffff>] 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/