linux-kernel - Re: [PATCH 1/9] exec_path 1/9: introduce ->exec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.01.0906050848520.6847@localhost.localdomain>
Date:	Fri, 5 Jun 2009 08:49:56 -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:
> 
> 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-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/