| |||||||||||||
|
| |||||||||||||
Detecting kernel memory leaksDetecting kernel memory leaksPosted Jun 23, 2006 4:40 UTC (Fri) by cpeterso (subscriber, #305)In reply to: Detecting kernel memory leaks by flewellyn Parent article: Detecting kernel memory leaks
I remember reading a LKML comment by Linus that he would never add a garbage collector to the kernel. Maybe one day, he'll eat those words. :-) I definitely think it's worth investigating, especially given these new memleak patches.
(Log in to post comments)
Detecting kernel memory leaks Posted Jun 24, 2006 11:59 UTC (Sat) by nix (subscriber, #2304) [Link] net/unix/garbage.c already contains a mark-and-sweep garbage collector: garbage collection is a requirement for AF_UNIX socket handling unless you like DoSes (which are easy: a program sets up an AF_UNIX socket, opens it itself but does not go into accept(), sends the socket's filehandle along the socket, closes both ends, and quits. Oops. One handle leaked, unless you detect the filehandles in transit along the the AF_UNIX socket, which means mark-and-sweep collection given that these fhes may be the fhes of other sockets which may themselves have filehandles in transit along them...)
|
|
||||||||||||