All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/2] move binfmt filed to signal_struct
Date: Fri, 24 Jul 2009 09:15:55 +0900	[thread overview]
Message-ID: <4A68FD3B.7040606@ct.jp.nec.com> (raw)
In-Reply-To: <20090723161806.GA5690@redhat.com>

Oleg Nesterov wrote:
> On 07/22, Roland McGrath wrote:
>>>> 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.
> 
> Ah, agreed.
> 
> Hiroshi, what do you think?

yeah, it sounds better. I'll try to update.

Thanks,
Hiroshi

  reply	other threads:[~2009-07-24  0:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  8:42 [RFC 1/2] move binfmt filed to signal_struct Hiroshi Shimamoto
2009-07-10  8:43 ` [RFC 2/2] make binfmt module get and put per signal_struct Hiroshi Shimamoto
2009-07-22 20:23 ` [RFC 1/2] move binfmt filed to signal_struct Andrew Morton
2009-07-22 22:03   ` Roland McGrath
2009-07-23 16:18     ` Oleg Nesterov
2009-07-24  0:15       ` Hiroshi Shimamoto [this message]
2009-07-24  4:15         ` [PATCH 1/2] task_struct cleanup: move binfmt field to mm_struct Hiroshi Shimamoto
2009-07-24  4:17           ` [PATCH 2/2] task_struct cleanup: make binfmt module get and put per mm_struct Hiroshi Shimamoto
2009-07-24 16:14           ` [PATCH 1/2] task_struct cleanup: move binfmt field to mm_struct Oleg Nesterov
2009-07-27  0:27             ` Hiroshi Shimamoto
2009-07-27 16:59               ` Oleg Nesterov
2009-07-28  6:21                 ` Hiroshi Shimamoto
2009-07-28 14:37                   ` Oleg Nesterov
2009-07-30  0:42                     ` [PATCH 0/1] " Hiroshi Shimamoto
2009-07-30  0:43                       ` [PATCH 1/1] " Hiroshi Shimamoto
2009-07-30 17:55                         ` Oleg Nesterov
2009-07-30 19:27                           ` Roland McGrath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A68FD3B.7040606@ct.jp.nec.com \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.