Re: [PATCH 08/12] add trace events for each syscall entry/exit

From: Steven Rostedt
Date: Wed Aug 26 2009 - 10:43:41 EST

On Wed, 26 Aug 2009, Heiko Carstens wrote:
> > Ah, there are callsites that use kernel_thread() directly?
> > Does it means that t->mm could be non NULL for such resulting
> > kernel threads, in that case it would be hard to hook on
> > do_fork() to check that.
> Oh yes, you are right. kernel threads created with kernel_thread()
> have t->mm != NULL if the forking process has an mm too.
> There are very few callsites left which still use kernel_thread().
> (the last one in s390 driver code will be gone after the next
> merge window).
> As far as I can there are only four callsites left
> (excluding staging): jffs2 and three in net/bluetooth/*

Ouch! Those need to be fixed.


-- Steve

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at