From: Andrew Morton <akpm@osdl.org>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: suresh.b.siddha@intel.com, discuss@x86-64.org,
linux-kernel@vger.kernel.org, ak@suse.de, nanhai.zou@intel.com,
rohit.seth@intel.com, rajesh.shah@intel.com
Subject: Re: [Patch] x86_64: TASK_SIZE fixes for compatibility mode processes
Date: Thu, 2 Jun 2005 15:48:23 -0700 [thread overview]
Message-ID: <20050602154823.15141bfc.akpm@osdl.org> (raw)
In-Reply-To: <20050602151912.B14384@unix-os.sc.intel.com>
"Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
>
> On Thu, Jun 02, 2005 at 01:50:13PM -0700, Andrew Morton wrote:
> > "Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
> > >
> > > +#define TASK_SIZE_OF(child) ((test_tsk_thread_flag(child, TIF_IA32)) ? IA32_PAGE_OFFSET : TASK_SIZE64)
> >
> > The task size is an attribute of the task's mm_struct, not of the task.
>
> ia64, ppc64 and s390 seems be getting this info from thread_info or
> thread_struct in the task struct.
I know. I'm claiming that this is conceptually wrong.
> > The place where this tends to come unstuck is when a 32-bit task holds a
> > reference on a 64-bit tasks's task_struct via a read of a /proc file. If
> > the 64-bit task exits then it is the 32-bit task who does the final freeing
> > of the 64-bit tasks's task_struct and mm_struct. (and all vice-versa, of
> > course). Will your patch handle this race scenario correctly?
>
> In recent kernels, instead of TASK_SIZE, "-1" is getting passed to unmap_vmas()
> from exit_mmap. Same case with ceiling (set to "0") for free_pgtables().
> It shouldn't be a problem with this, right?
Yeah, I recall that hack being added. Might work.
next prev parent reply other threads:[~2005-06-02 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 20:32 Siddha, Suresh B
2005-06-02 20:50 ` Andrew Morton
2005-06-02 22:19 ` Siddha, Suresh B
2005-06-02 22:48 ` Andrew Morton [this message]
2005-06-02 23:06 ` [discuss] " Siddha, Suresh B
2005-06-03 15:48 ` Andi Kleen
2005-06-03 19:09 ` Siddha, Suresh B
2005-06-05 11:17 ` Andi Kleen
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=20050602154823.15141bfc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=rajesh.shah@intel.com \
--cc=rohit.seth@intel.com \
--cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome