public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Lee Schermerhorn <lee.schermerhorn@hp.com>,
	Paul Menage <menage@google.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 3/4] cpuset: alloc nodemask_t at heap not stack
Date: Tue, 09 Mar 2010 09:29:06 +0800	[thread overview]
Message-ID: <4B95A462.2040201@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003081324550.14689@chino.kir.corp.google.com>

on 2010-3-9 5:27, David Rientjes wrote:
> On Mon, 8 Mar 2010, Miao Xie wrote:
> 
>> Changes from V1 to V2:
>> - None
>>
> 
> Both this and patch 2/4 are already in -mm, so please rebase this series 
> on mmotm-2010-03-04-18-05.

ok, I'll do it.

> 
>> @@ -1381,39 +1394,46 @@ static void cpuset_attach(struct cgroup_subsys *ss, struct cgroup *cont,
>>  			  struct cgroup *oldcont, struct task_struct *tsk,
>>  			  bool threadgroup)
>>  {
>> -	nodemask_t from, to;
>>  	struct mm_struct *mm;
>>  	struct cpuset *cs = cgroup_cs(cont);
>>  	struct cpuset *oldcs = cgroup_cs(oldcont);
>> +	NODEMASK_ALLOC(nodemask_t, from, GFP_KERNEL);
>> +	NODEMASK_ALLOC(nodemask_t, to, GFP_KERNEL);
>> +
>> +	if (from == NULL || to == NULL)
>> +		return;
>>  
> 
> You're potentially leaking one of the allocated nodemasks there if the 
> other is -ENOMEM.

Sorry for my mistake. I'll fix it in the next version.

Thanks!
Miao

> 
> 
> 



      reply	other threads:[~2010-03-09  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 10:07 [PATCH V2 3/4] cpuset: alloc nodemask_t at heap not stack Miao Xie
2010-03-08 21:27 ` David Rientjes
2010-03-09  1:29   ` Miao Xie [this message]

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=4B95A462.2040201@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=npiggin@suse.de \
    --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