On Fri, 5 Jun 2009, Alexey Dobriyan wrote: > > It's borrowed by kernel thread of course, not userspace task. .. and even if it is, what's the problem? That kernel thread has borroed whe VM for a while. It effectively _is_ a thread of the process now. So it's technically not even wrong to explicitly allow things like /proc/*/exe to see it as such. But you can hide it by just checking some flag in the thread structure if you really want to. But when creating a regular thread, you should _not_ need to take a spinlock and duplicate the executable path! Linus -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
