public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Wanpeng Li <liwp.linux@gmail.com>, Michal Hocko <mhocko@suse.cz>,
	Balbir Singh <bsingharora@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>, Arun Sharma <asharma@fb.com>,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH 1/5 v2] memcg: replace unsigned long by u64 to avoid overflow
Date: Mon, 25 Jun 2012 17:30:11 +0900	[thread overview]
Message-ID: <4FE82193.1070307@jp.fujitsu.com> (raw)
In-Reply-To: <20120625075215.GW27816@cmpxchg.org>

(2012/06/25 16:52), Johannes Weiner wrote:
> On Mon, Jun 25, 2012 at 02:04:20PM +0800, Wanpeng Li wrote:
>> Changlog:
>>
>> V2 -> V1:
>> * fix zone_page_state()::/include/linux/vmstat.h returns 'unsigned long'
>>
>> From: Wanpeng Li <liwp@linux.vnet.ibm.com>
>>
>> Since the return value variable in mem_cgroup_zone_nr_lru_pages and
>> mem_cgroup_node_nr_lru_pages functions are u64, so replace the return
>> value of funtions by u64 to avoid overflow.
>>
>> Signed-off-by: Wanpeng Li <liwp.linux@gmail.com>
>> ---
>>   include/linux/vmstat.h |    2 +-
>>   mm/memcontrol.c        |    5 ++---
>>   2 files changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/linux/vmstat.h b/include/linux/vmstat.h
>> index 65efb92..6a14291 100644
>> --- a/include/linux/vmstat.h
>> +++ b/include/linux/vmstat.h
>> @@ -106,7 +106,7 @@ static inline unsigned long global_page_state(enum zone_stat_item item)
>>   	return x;
>>   }
>>
>> -static inline unsigned long zone_page_state(struct zone *zone,
>> +static inline u64 zone_page_state(struct zone *zone,
>>   					enum zone_stat_item item)
>>   {
>>   	long x = atomic_long_read(&zone->vm_stat[item]);
>
> We established that there is no known reason to use ulong for page
> counters and that IF YOU HAD ONE, you should obviously say so and then
> do a wholesale conversion.  But I don't think you have one.
>
> This patch makes absolutely no sense.
>
I agree. Then, Nack from me.

Thanks,
-Kame



  reply	other threads:[~2012-06-25  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  6:04 [PATCH 1/5 v2] memcg: replace unsigned long by u64 to avoid overflow Wanpeng Li
2012-06-25  7:52 ` Johannes Weiner
2012-06-25  8:30   ` Kamezawa Hiroyuki [this message]
2012-07-04 12:24     ` Wanpeng Li
2012-07-04 12:29       ` Glauber Costa
2012-07-04 13:16         ` Johannes Weiner
2012-07-04 13:18           ` Glauber Costa

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=4FE82193.1070307@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=asharma@fb.com \
    --cc=bsingharora@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=eric.dumazet@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwp.linux@gmail.com \
    --cc=mhocko@suse.cz \
    --cc=vapier@gentoo.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