public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Janak Desai <janak@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] (repost) New System call, unshare (fwd)
Date: Thu, 08 Sep 2005 11:37:07 +1000	[thread overview]
Message-ID: <431F95C3.8010200@yahoo.com.au> (raw)
In-Reply-To: <Pine.WNT.4.63.0509071350080.4008@IBM-AIP3070F3AM>

Janak Desai wrote:


> -	tsk->min_flt = tsk->maj_flt = 0;
> -	tsk->nvcsw = tsk->nivcsw = 0;
> +	/*
> +	 * If the process memory is being duplicated as part of the
> +	 * unshare system call, we are working with the current process
> +	 * and not a newly allocated task strucutre, and should not
> +	 * zero out fault info, context switch counts, mm and active_mm
> +	 * fields.
> +	 */
> +	if (copy_share_action == MAY_SHARE) {
> +		tsk->min_flt = tsk->maj_flt = 0;
> +		tsk->nvcsw = tsk->nivcsw = 0;
>  

Why don't you just do this in copy_process?

> -	tsk->mm = NULL;
> -	tsk->active_mm = NULL;
> +		tsk->mm = NULL;
> +		tsk->active_mm = NULL;
> +	}
>  
>  	/*
>  	 * Are we cloning a kernel thread?
> @@ -1002,7 +1023,7 @@ static task_t *copy_process(unsigned lon
>  		goto bad_fork_cleanup_fs;
>  	if ((retval = copy_signal(clone_flags, p)))
>  		goto bad_fork_cleanup_sighand;
> -	if ((retval = copy_mm(clone_flags, p)))
> +	if ((retval = copy_mm(clone_flags, p, MAY_SHARE)))
>  		goto bad_fork_cleanup_signal;
>  	if ((retval = copy_keys(clone_flags, p)))
>  		goto bad_fork_cleanup_mm;
> @@ -1317,3 +1338,172 @@ void __init proc_caches_init(void)
>  			sizeof(struct mm_struct), 0,
>  			SLAB_HWCACHE_ALIGN|SLAB_PANIC, NULL, NULL);
>  }
> +
> +/*
> + * unshare_mm is called from the unshare system call handler function to
> + * make a private copy of the mm_struct structure. It calls copy_mm with
> + * CLONE_VM flag cleard, to ensure that a private copy of mm_struct is made,
> + * and with mm_copy_share enum set to UNSHARE, to ensure that copy_mm
> + * does not clear fault info, context switch counts, mm and active_mm
> + * fields of the mm_struct.
> + */
> +static int unshare_mm(unsigned long unshare_flags, struct task_struct *tsk)
> +{
> +	int retval = 0;
> +	struct mm_struct *mm = tsk->mm;
> +
> +	/*
> +	 * If the virtual memory is being shared, make a private
> +	 * copy and disassociate the process from the shared virtual
> +	 * memory.
> +	 */
> +	if (atomic_read(&mm->mm_users) > 1) {
> +		retval = copy_mm((unshare_flags & ~CLONE_VM), tsk, UNSHARE);
> +
> +		/*
> +		 * If copy_mm was successful, decrement the number of users
> +		 * on the original, shared, mm_struct.
> +		 */
> +		if (!retval)
> +			atomic_dec(&mm->mm_users);
> +	}
> +	return retval;
> +}
> +

What prevents thread 1 from decrementing mm_users after thread 2 has
found it to be 2?

-- 
SUSE Labs, Novell Inc.


Send instant messages to your online friends http://au.messenger.yahoo.com 

  parent reply	other threads:[~2005-09-08  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 17:51 [PATCH 1/2] (repost) New System call, unshare (fwd) Janak Desai
2005-09-07 21:12 ` Chris Wright
2005-09-08  2:31   ` Janak Desai
2005-09-09  2:01   ` Janak Desai
2005-09-08  1:37 ` Nick Piggin [this message]
2005-09-09  2:06   ` Janak Desai

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=431F95C3.8010200@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=janak@us.ibm.com \
    --cc=linux-kernel@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