[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b84fa328-91c2-fe02-da17-993236d91c81@alu.unizg.hr>
Date: Thu, 18 May 2023 10:00:36 +0200
From: Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Mirsad Goran Todorovac <mirsad.goran.todorovac@....hr>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-input@...r.kernel.org,
Benjamin Tissoires <benjamin.tissoires@...hat.com>,
Jiri Kosina <jikos@...nel.org>
Subject: Re: [BUG][NEW DATA] Kmemleak, possibly hiddev_connect(), in 6.3.0+
torvalds tree commit gfc4354c6e5c2
On 5/17/23 20:57, Greg Kroah-Hartman wrote:
> And leaks are hard to notice, especially ones that only show up when you
> remove a specific type of device.
>
> thanks again for your help here,
I feel like more of a hindrance from the real issues than being helpful.
Memory leaks seem easy to detect, however, building with KMEMLEAK
debugging on can take up to 50-67% of system time, as I've noticed
a couple of days ago ...
It is obviously incurring some overhead. I did not expect a kernel compilation
as computation-heavy process to have such an impact from memory object
debugging.
Best regards,
Mirsad
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
"What’s this thing suddenly coming towards me very fast? Very very fast.
... I wonder if it will be friends with me?"
Powered by blists - more mailing lists