mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kanoj Sarcar <kanojsarcar@yahoo.com>
To: Colin Gibbs <colin@gibbs.dhs.org>, linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: Re: bug in fork failure path?
Date: Thu, 18 Apr 2002 18:27:57 -0700 (PDT)	[thread overview]
Message-ID: <20020419012757.24839.qmail@web14305.mail.yahoo.com> (raw)
In-Reply-To: <1019178622.25887.630.camel@monolith>


--- Colin Gibbs <colin@gibbs.dhs.org> wrote:
> Hi, 
> 
> I came across this bug hacking on sparc32. If fork
> fails in copy_mm ->
> dup_mmap, destroy_context is called on the new mm
> before
> init_new_context. 

Yes, this definitely sounds like a bug. I added the
init_new_context() call for mips64 in 2.3. With the
way the current code is, I belive even mips64 has
a problem.

Kanoj

> 
> fork.c:330 
> 	retval = -ENOMEM; 
> 	mm = allocate_mm(); 
> 	if (!mm) 
> 		goto fail_nomem; 
> 
> 	/* Copy the current MM stuff.. */ 
> 	memcpy(mm, oldmm, sizeof(*mm)); 
> 	if (!mm_init(mm)) 
> 		goto fail_nomem; 
> 
> Failure is ok here. We don't try to do an mmput, but
> we have memcpy'd
> the mm struct context and all. 
> 
> 	down_write(&oldmm->mmap_sem); 
> 	retval = dup_mmap(mm); 
> 	up_write(&oldmm->mmap_sem); 
> 
> 	if (retval) 
> 		goto free_pt; 
> 
> If we fail and call mmput, destroy_context gets
> called before
> init_new_context below. This removes the parent
> process's context since
> it was just memcpy'd from the parent's mm struct. 
> 
> 	/* 
> 	 * child gets a private LDT (if there was an LDT in
> the parent) 
> 	 */ 
> 	copy_segments(tsk, mm); 
> 
> 	if (init_new_context(tsk,mm)) 
> 		goto free_pt; 
> 
> Can we move the init_new_context to just after the
> mm_init call? Works
> nicely on sparc. Most archs have a fairly trivial
> init_new_context
> anyway. 
> 
> Colin 
> 
> --- 2.4.19-pre4/kernel/fork.c	Thu Mar 28 19:49:36
> 2002
> +++ tortoise-19-pre4/kernel/fork.c	Wed Apr 17
> 23:26:20 2002
> @@ -336,6 +336,9 @@
>  	if (!mm_init(mm))
>  		goto fail_nomem;
>  
> +	if (init_new_context(tsk,mm))
> +		goto free_pt;
> +
>  	down_write(&oldmm->mmap_sem);
>  	retval = dup_mmap(mm);
>  	up_write(&oldmm->mmap_sem);
> @@ -347,9 +350,6 @@
>  	 * child gets a private LDT (if there was an LDT
> in the parent)
>  	 */
>  	copy_segments(tsk, mm);
> -
> -	if (init_new_context(tsk,mm))
> -		goto free_pt;
>  
>  good_mm:
>  	tsk->mm = mm;
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
http://vger.kernel.org/majordomo-info.html


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

  reply	other threads:[~2002-04-19  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19  1:10 Colin Gibbs
2002-04-19  1:27 ` Kanoj Sarcar [this message]
2002-05-08  0:06 ` David S. Miller

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=20020419012757.24839.qmail@web14305.mail.yahoo.com \
    --to=kanojsarcar@yahoo.com \
    --cc=colin@gibbs.dhs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®