[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906050942450.6847@localhost.localdomain>
Date: Fri, 5 Jun 2009 09:48:02 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alexey Dobriyan <adobriyan@...il.com>
cc: Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Matt Helsley <matthltc@...ibm.com>, xemul@...allels.com,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, dave@...ux.vnet.ibm.com,
mingo@...e.hu, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 1/9] exec_path 1/9: introduce ->exec_path and switch
/proc/*/exe
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists