From: Michal Hocko <mhocko@suse.cz>
To: Sha Zhengju <handai.szj@gmail.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
nishimura@mxp.nes.nec.co.jp, akpm@linux-foundation.org,
jeff.liu@oracle.com, Sha Zhengju <handai.szj@taobao.com>
Subject: Re: [PATCH 2/3] memcg: check more strictly to avoid PAGE_ALIGN wrapped to 0
Date: Tue, 7 May 2013 16:04:02 +0200 [thread overview]
Message-ID: <20130507140402.GC9497@dhcp22.suse.cz> (raw)
In-Reply-To: <1367768590-4403-1-git-send-email-handai.szj@taobao.com>
On Sun 05-05-13 23:43:10, Sha Zhengju wrote:
> Since PAGE_ALIGN is aligning up(the next page boundary), this can
> prevent input values wrapped to 0 and cause strange result to user.
I guess you wanted to say that it can cause an overflow, right?
"
Since PAGE_ALIGN is aligning up (to the next page boundary), this can
cause an overflow to 0 if >= ULLONG_MAX-4094 value is given in the
buffer.
"
>
> This patch also rename the second arg of
> res_counter_memparse_write_strategy() to 'resp' and add a local
> variable 'res' to save the too often dereferences. Thanks Andrew
> for pointing it out!
Again, it would be nicer to have this cleanup in a separate patch.
> Signed-off-by: Sha Zhengju <handai.szj@taobao.com>
> Reported-by: Li Wenpeng <xingke.lwp@taobao.com>
Acked-by: Michal Hocko <mhocko@suse.cz>
We have this bug since ever and nobody has noticed so nobody seems to
use
> ---
> kernel/res_counter.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/res_counter.c b/kernel/res_counter.c
> index 3f0417f..be8ddda 100644
> --- a/kernel/res_counter.c
> +++ b/kernel/res_counter.c
> @@ -178,23 +178,29 @@ u64 res_counter_read_u64(struct res_counter *counter, int member)
> #endif
>
> int res_counter_memparse_write_strategy(const char *buf,
> - unsigned long long *res)
> + unsigned long long *resp)
> {
> char *end;
> + unsigned long long res;
>
> /* return RES_COUNTER_MAX(unlimited) if "-1" is specified */
> if (*buf == '-') {
> - *res = simple_strtoull(buf + 1, &end, 10);
> - if (*res != 1 || *end != '\0')
> + res = simple_strtoull(buf + 1, &end, 10);
> + if (res != 1 || *end != '\0')
> return -EINVAL;
> - *res = RES_COUNTER_MAX;
> + *resp = RES_COUNTER_MAX;
> return 0;
> }
>
> - *res = memparse(buf, &end);
> + res = memparse(buf, &end);
> if (*end != '\0')
> return -EINVAL;
>
> - *res = PAGE_ALIGN(*res);
> + if (PAGE_ALIGN(res) >= res)
> + res = PAGE_ALIGN(res);
> + else
> + res = RES_COUNTER_MAX; /* avoid PAGE_ALIGN wrapping to zero */
> +
> + *resp = res;
> return 0;
> }
> --
> 1.7.9.5
>
--
Michal Hocko
SUSE Labs
--
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>
next prev parent reply other threads:[~2013-05-07 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 15:43 Sha Zhengju
2013-05-07 14:04 ` Michal Hocko [this message]
2013-05-07 15:41 ` 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=20130507140402.GC9497@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=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