linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kautuk Consul <consul.kautuk@gmail.com>,
	Joe Perches <joe@perches.com>,
	Minchan Kim <minchan.kim@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mm/vmalloc.c: eliminate extra loop in pcpu_get_vm_areas error path
Date: Tue, 22 Nov 2011 21:34:25 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1111222134080.21009@chino.kir.corp.google.com> (raw)
In-Reply-To: <20111118115955.410af035.akpm@linux-foundation.org>

On Fri, 18 Nov 2011, Andrew Morton wrote:

> > If either of the vas or vms arrays are not properly kzalloced,
> > then the code jumps to the err_free label.
> > 
> > The err_free label runs a loop to check and free each of the array
> > members of the vas and vms arrays which is not required for this
> > situation as none of the array members have been allocated till this
> > point.
> > 
> > Eliminate the extra loop we have to go through by introducing a new
> > label err_free2 and then jumping to it.
> > 
> > Signed-off-by: Kautuk Consul <consul.kautuk@gmail.com>
> > ---
> >  mm/vmalloc.c |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> > 
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > index b669aa6..1a0d4e2 100644
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -2352,7 +2352,7 @@ struct vm_struct **pcpu_get_vm_areas(const unsigned long *offsets,
> >  	vms = kzalloc(sizeof(vms[0]) * nr_vms, GFP_KERNEL);
> >  	vas = kzalloc(sizeof(vas[0]) * nr_vms, GFP_KERNEL);
> >  	if (!vas || !vms)
> > -		goto err_free;
> > +		goto err_free2;
> >  
> >  	for (area = 0; area < nr_vms; area++) {
> >  		vas[area] = kzalloc(sizeof(struct vmap_area), GFP_KERNEL);
> > @@ -2455,6 +2455,7 @@ err_free:
> >  		if (vms)
> >  			kfree(vms[area]);
> >  	}
> > +err_free2:
> >  	kfree(vas);
> >  	kfree(vms);
> >  	return NULL;
> 
> Which means we can also do the below, yes?  (please check my homework!)
> 
> --- a/mm/vmalloc.c~mm-vmallocc-eliminate-extra-loop-in-pcpu_get_vm_areas-error-path-fix
> +++ a/mm/vmalloc.c
> @@ -2449,10 +2449,8 @@ found:
>  
>  err_free:
>  	for (area = 0; area < nr_vms; area++) {
> -		if (vas)
> -			kfree(vas[area]);
> -		if (vms)
> -			kfree(vms[area]);
> +		kfree(vas[area]);
> +		kfree(vms[area]);
>  	}
>  err_free2:
>  	kfree(vas);

On both patches:

Acked-by: David Rientjes <rientjes@google.com>

--
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>

      parent reply	other threads:[~2011-11-23  5:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 11:43 Kautuk Consul
2011-11-18 19:59 ` Andrew Morton
2011-11-19  3:32   ` kautuk.c @samsung.com
2011-11-23  5:34   ` David Rientjes [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=alpine.DEB.2.00.1111222134080.21009@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=consul.kautuk@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --cc=paulmck@linux.vnet.ibm.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