linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	David Rientjes <rientjes@google.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Nazarewicz <mina86@mina86.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	John Stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH 1/2] break out page allocation warning code
Date: Wed, 20 Apr 2011 11:19:52 +0900 (JST)	[thread overview]
Message-ID: <20110420112006.461A.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110420105059.460C.A69D9226@jp.fujitsu.com>

> The concept is ok to me. but AFAIK some caller are now using ARRAY_SIZE(tsk->comm).
> or sizeof(tsk->comm). Probably callers need to be changed too.

one more correction.

>  void set_task_comm(struct task_struct *tsk, char *buf)
>  {
> +	char tmp_comm[TASK_COMM_LEN];
> +
>  	task_lock(tsk);
>  
> +	memcpy(tmp_comm, tsk->comm_buf, TASK_COMM_LEN);
> +	tsk->comm = tmp;
>  	/*
> -	 * Threads may access current->comm without holding
> -	 * the task lock, so write the string carefully.
> -	 * Readers without a lock may see incomplete new
> -	 * names but are safe from non-terminating string reads.
> +	 * Make sure no one is still looking at tsk->comm_buf
>  	 */
> -	memset(tsk->comm, 0, TASK_COMM_LEN);
> -	wmb();
> -	strlcpy(tsk->comm, buf, sizeof(tsk->comm));
> +	synchronize_rcu();

The doc says,

/**
 * synchronize_rcu - wait until a grace period has elapsed.
 *

And here is under spinlock.



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-04-20  2:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 17:04 Dave Hansen
2011-04-15 17:04 ` [PATCH 2/2] print vmalloc() state after allocation failures Dave Hansen
2011-04-15 17:20   ` Michal Nazarewicz
2011-04-15 17:44     ` Dave Hansen
2011-04-17  0:03       ` David Rientjes
2011-04-18 15:21         ` Dave Hansen
2011-04-17  0:02 ` [PATCH 1/2] break out page allocation warning code David Rientjes
2011-04-18 15:10   ` Dave Hansen
2011-04-18 20:25     ` David Rientjes
2011-04-18 20:57       ` Dave Hansen
2011-04-19 21:23         ` David Rientjes
2011-04-18 21:03       ` Dave Hansen
2011-04-18 21:22       ` Dave Hansen
2011-04-19  0:44         ` KOSAKI Motohiro
2011-04-19 21:21           ` David Rientjes
2011-04-20  0:39             ` KOSAKI Motohiro
2011-04-20 20:24               ` David Rientjes
2011-04-20 20:34                 ` john stultz
2011-04-21  1:29                   ` KOSAKI Motohiro
2011-04-25  4:21                     ` KOSAKI Motohiro
2011-04-26 19:27                     ` john stultz
2011-04-27 23:51                       ` David Rientjes
2011-04-28  0:32                         ` john stultz
2011-04-28  1:29                           ` john stultz
2011-04-28 22:48                             ` David Rientjes
2011-04-28 23:48                               ` john stultz
2011-04-29  0:04                                 ` john stultz
2011-04-26 21:25                     ` john stultz
2011-04-28  3:05                       ` KOSAKI Motohiro
2011-04-20  1:41             ` Dave Hansen
2011-04-20  1:50               ` KOSAKI Motohiro
2011-04-20  2:19                 ` KOSAKI Motohiro [this message]
2011-04-20  2:46                   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2011-04-19 16:21 Dave Hansen
2011-04-08 20:22 Dave Hansen
2011-04-08 20:37 ` David Rientjes
2011-04-08 20:43   ` Dave Hansen
2011-04-08 20:54 ` Michał Nazarewicz
2011-04-08 21:02   ` Dave Hansen
2011-04-11 10:20     ` Michal Nazarewicz

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=20110420112006.461A.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mina86@mina86.com \
    --cc=rientjes@google.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