Dear Taha... > I have tried a number of examples of device drivers. > But I am not sure how to check for memory leaks... Avishay and Mauricio already gave you good hints, so I will just add another comment. Sometimes it is hard to differentiate between leak and unused memory area. I suggest to do code analysis first, for example make sure every kmalloc-ed memory block is followed by kfree() and so on. Also, it will be a good idea if you test your driver in the minimal setup, e.g: under single user mode with minimum daemons loaded. it will ease you to determine the source of memory leak. NB: Don't worry if you find it hard to follow the discussions here. That is why God introduces "learning curve" to human ;) A regards Mulyadi -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
