On Wed, 18 May 2011 08:25:54 +0200 Ingo Molnar <mingo@xxxxxxx> wrote: > " Hey, this looks a bit racy and 'top' very rarely, on rare workloads that > play with ->comm[], might display a weird reading task name for a second, > amongst the many other temporarily nonsensical statistical things it > already prints every now and then. " Well we should at least make sure that `top' won't run off the end of comm[] and go oops. I think that's guaranteed by the fact(s) that init_tasks's comm[15] is zero and is always copied-by-value across fork and can never be overwritten in any task_struct. But I didn't check that. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>