On Thu, 2009-01-15 at 13:05 +0100, Heiko Carstens wrote:
> Btw. you have
>
> /*
> * Stop the automatic memory scanning thread. This function must be called
> * with the kmemleak_mutex held.
> */
> void stop_scan_thread(void)
> {
> ...
>
> but call the function unlocked from kmemleak_write. Looks like a bug ;)
kmemleak_write() is called with the kmemleak_mutex acquired in the
kmemleak_open() function (and released in kmemleak_release()).
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
