Messages in this thread | | | Date | Fri, 26 Jun 2009 10:07:39 +0300 | Subject | Re: kmemleak suggestion (long message) | From | Pekka Enberg <> |
| |
Hi Ingo,
* Sergey Senozhatsky <sergey.senozhatsky@mail.by> wrote: >> Currently kmemleak prints info about all objects. I guess >> sometimes kmemleak gives you more than you actually need.
On Fri, Jun 26, 2009 at 9:59 AM, Ingo Molnar<mingo@elte.hu> wrote: > It prints _a lot_ of info and spams the syslog. I lost crash info a > few days ago due to that: by the time i inspected a crashed machine > the tons of kmemleak output scrolled out the crash from the dmesg > buffer. > > This is not acceptable. > > Instead it should perhaps print _at most_ a single line every few > minutes, printing a summary about _how many_ leaked entries it > suspects, and should offer a /debug/mm/kmemleak style of file where > the entries can be read out from.
Yup, makes tons of sense.
Pekka
| |