MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Roland McGrath <roland@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
       linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [RFC 1/2] move binfmt filed to signal_struct
In-Reply-To: Andrew Morton's message of  Wednesday, 22 July 2009 13:23:02 -0700 <20090722132302.a9889eb3.akpm@linux-foundation.org>
References: <4A56FEF7.80207@ct.jp.nec.com>
	<20090722132302.a9889eb3.akpm@linux-foundation.org>
Message-Id: <20090722220353.88B2A67B6E@magilla.sf.frob.com>
Date: Wed, 22 Jul 2009 15:03:53 -0700 (PDT)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 896
Lines: 24

> > Because the binfmt is not different between threads in the same process,
> > it can be moved from task_struct to signal_struct.
> 
> Seems like a logical cleanup to me.

IMHO binfmt belongs in mm_struct.

> We should rename signal_struct.

Indeed, it's in fact 'struct process'.  But historically Linus has objected
to admitting that there is really a concept of process in the POSIX sense
that exists deep in the implementation (as it truly does for years now),
beyond "tasks that happen to share a lot of CLONE_* stuff".  The name
signal_struct is sufficiently misleading to make it easier to retain the
fantasy he prefers. ;-)


Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/