From: Sha Zhengju <handai.szj@gmail.com>
To: cgroups@vger.kernel.org, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, jeff.liu@oracle.com,
Sha Zhengju <handai.szj@taobao.com>
Subject: [PATCH] memcg: Check more strictly to avoid ULLONG overflow by PAGE_ALIGN
Date: Fri, 12 Apr 2013 14:39:23 +0800 [thread overview]
Message-ID: <1365748763-4350-1-git-send-email-handai.szj@taobao.com> (raw)
From: Sha Zhengju <handai.szj@taobao.com>
While writing memory.limit_in_bytes, a confusing result may happen:
$ mkdir /memcg/test
$ cat /memcg/test/memory.limit_in_bytes
9223372036854775807
$ cat /memcg/test/memory.memsw.limit_in_bytes
9223372036854775807
$ echo 18446744073709551614 > /memcg/test/memory.limit_in_bytes
$ cat /memcg/test/memory.limit_in_bytes
0
Strangely, the write successed and reset the limit to 0.
The patch corrects RESOURCE_MAX and fixes this kind of overflow.
Signed-off-by: Sha Zhengju <handai.szj@taobao.com>
Reported-by: Li Wenpeng < xingke.lwp@taobao.com>
Cc: Jie Liu <jeff.liu@oracle.com>
---
include/linux/res_counter.h | 2 +-
kernel/res_counter.c | 8 +++++++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/include/linux/res_counter.h b/include/linux/res_counter.h
index c230994..c2f01fc 100644
--- 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
/**
* 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);
+
return 0;
}
--
1.7.9.5
--
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 reply other threads:[~2013-04-12 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 6:39 Sha Zhengju [this message]
2013-04-12 8:11 ` Daisuke Nishimura
2013-04-12 10:38 ` Sha Zhengju
2013-04-15 20:58 ` Andrew Morton
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=1365748763-4350-1-git-send-email-handai.szj@taobao.com \
--to=handai.szj@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=handai.szj@taobao.com \
--cc=jeff.liu@oracle.com \
--cc=linux-mm@kvack.org \
/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