On Fri, 5 Jun 2009, Alexey Dobriyan wrote: > > This mapping issue is what created VM_EXECUTABLE/MAP_EXECUTABLE in > the first place, I assume? Never mind it's cheap hack. > > > and goes along with task->mm, and should be there, not in task_struct. > > Because ->mm can be borrowed to unrelated task and user has to check > for it. Not it can't. You're confusing ->mm with ->active_mm. The latter can be borrowed. The former can not. The fact is, the executable is _inherently_ tied to the mm. It's what it is mapped into. It makes no sense to tie it to anything else. It's simply fundamentally not a "per-thread" thing. 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
