linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Sha Zhengju <handai.szj@gmail.com>,
	cgroups@vger.kernel.org, linux-mm@kvack.org, jeff.liu@oracle.com,
	Sha Zhengju <handai.szj@taobao.com>
Subject: Re: [PATCH] memcg: Check more strictly to avoid ULLONG overflow by PAGE_ALIGN
Date: Mon, 15 Apr 2013 13:58:05 -0700	[thread overview]
Message-ID: <20130415135805.c552511917b0dbe113388acb@linux-foundation.org> (raw)
In-Reply-To: <20130412171108.d3ef3e2d66e9c1bfcf69467c@mxp.nes.nec.co.jp>

On Fri, 12 Apr 2013 17:11:08 +0900 Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:

> > --- a/include/linux/res_counter.h
> > +++ b/include/linux/res_counter.h
> > @@ -54,7 +54,7 @@ struct res_counter {
> >  	struct res_counter *parent;
> >  };
> >  
> > -#define RESOURCE_MAX (unsigned long long)LLONG_MAX
> > +#define RESOURCE_MAX (unsigned long long)ULLONG_MAX
> >  
> 
> I don't think it's a good idea to change a user-visible value.

The old value was a mistake, surely.

RESOURCE_MAX shouldn't be in this header file - that is far too general
a name.  I suggest the definition be moved to res_counter.c.  And the
(unsigned long long) cast is surely unneeded if we're to use
ULLONG_MAX.

> >  /**
> >   * Helpers to interact with userspace
> > diff --git a/kernel/res_counter.c b/kernel/res_counter.c
> > index ff55247..6c35310 100644
> > --- a/kernel/res_counter.c
> > +++ b/kernel/res_counter.c
> > @@ -195,6 +195,12 @@ int res_counter_memparse_write_strategy(const char *buf,
> >  	if (*end != '\0')
> >  		return -EINVAL;
> >  
> > -	*res = PAGE_ALIGN(*res);
> > +	/* Since PAGE_ALIGN is aligning up(the next page boundary),
> > +	 * check the left space to avoid overflow to 0. */
> > +	if (RESOURCE_MAX - *res < PAGE_SIZE - 1)
> > +		*res = RESOURCE_MAX;
> > +	else
> > +		*res = PAGE_ALIGN(*res);
> > +
> 
> Current interface seems strange because we can set a bigger value than
> the value which means "unlimited".

I'm not sure what you mean by this?

> So, how about some thing like:
> 
> 	if (*res > RESOURCE_MAX)
> 		return -EINVAL;
> 	if (*res > PAGE_ALIGN(RESOURCE_MAX) - PAGE_SIZE)
> 		*res = RESOURCE_MAX;
> 	else
> 		*res = PAGE_ALIGN(*res);
> 

The first thing I'd do to res_counter_memparse_write_strategy() is to
rename its second arg to `resp' then add a local called `res'.  Because
that function dereferences res far too often.

Then,

-	*res = PAGE_ALIGN(*res);
	if (PAGE_ALIGN(res) >= res)
		res = PAGE_ALIGN(res);
	else
		res = RESOURCE_MAX;	/* PAGE_ALIGN wrapped to zero */

	*resp = res;
	return 0;
	
	

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2013-04-15 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  6:39 Sha Zhengju
2013-04-12  8:11 ` Daisuke Nishimura
2013-04-12 10:38   ` Sha Zhengju
2013-04-15 20:58   ` Andrew Morton [this message]
2013-04-16  1:29     ` Daisuke Nishimura
2013-04-16  7:30       ` Sha Zhengju
2013-04-16 22:30       ` Andrew Morton
2013-04-16  7:29     ` Sha Zhengju

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=20130415135805.c552511917b0dbe113388acb@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=handai.szj@gmail.com \
    --cc=handai.szj@taobao.com \
    --cc=jeff.liu@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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