From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg Thelen <gthelen@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
David Rientjes <rientjes@google.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [BUGFIX] memcg: fix res_counter_read_u64 lock aware (Was Re: [PATCH] oom: handle overflow in mem_cgroup_out_of_memory()
Date: Thu, 27 Jan 2011 10:24:18 +0900 [thread overview]
Message-ID: <20110127102418.fc200c96.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20110126170824.ef2ab571.akpm@linux-foundation.org>
On Wed, 26 Jan 2011 17:08:24 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 27 Jan 2011 09:53:42 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> > res_counter_read_u64 reads u64 value without lock. It's dangerous
> > in 32bit environment. This patch adds lock.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> > include/linux/res_counter.h | 13 ++++++++++++-
> > kernel/res_counter.c | 2 +-
> > 2 files changed, 13 insertions(+), 2 deletions(-)
> >
> > Index: mmotm-0125/include/linux/res_counter.h
> > ===================================================================
> > --- mmotm-0125.orig/include/linux/res_counter.h
> > +++ mmotm-0125/include/linux/res_counter.h
> > @@ -68,7 +68,18 @@ struct res_counter {
> > * @pos: and the offset.
> > */
> >
> > -u64 res_counter_read_u64(struct res_counter *counter, int member);
> > +u64 res_counter_read_u64_locked(struct res_counter *counter, int member);
> > +
> > +static inline u64 res_counter_read_u64(struct res_counter *counter, int member)
> > +{
> > + unsigned long flags;
> > + u64 ret;
> > +
> > + spin_lock_irqsave(&counter->lock, flags);
> > + ret = res_counter_read_u64_locked(counter, member);
> > + spin_unlock_irqrestore(&counter->lock, flags);
> > + return ret;
> > +}
> >
> > ssize_t res_counter_read(struct res_counter *counter, int member,
> > const char __user *buf, size_t nbytes, loff_t *pos,
> > Index: mmotm-0125/kernel/res_counter.c
> > ===================================================================
> > --- mmotm-0125.orig/kernel/res_counter.c
> > +++ mmotm-0125/kernel/res_counter.c
> > @@ -126,7 +126,7 @@ ssize_t res_counter_read(struct res_coun
> > pos, buf, s - buf);
> > }
> >
> > -u64 res_counter_read_u64(struct res_counter *counter, int member)
> > +u64 res_counter_read_u64_locked(struct res_counter *counter, int member)
> > {
> > return *res_counter_member(counter, member);
> > }
>
> We don't need the lock on 64-bit platforms!
>
All res_counter function doesn't handle 32/64 bit differences. So, I did
in this style for now.
> And there's zero benefit to inlining the spin_lock/unlock(), given that
> the function will always be making a function call anyway.
>
Ok.
> See i_size_read() for inspiration.
>
I hate res_counter ;) I'll update patch.
Thanks,
-Kame
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-27 1:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 8:29 Greg Thelen
2011-01-26 13:40 ` Balbir Singh
2011-01-26 17:07 ` Johannes Weiner
2011-01-26 17:33 ` Greg Thelen
2011-01-26 18:30 ` Johannes Weiner
2011-01-26 20:32 ` Greg Thelen
2011-01-26 22:29 ` Andrew Morton
2011-01-27 0:24 ` KAMEZAWA Hiroyuki
2011-01-27 0:53 ` [BUGFIX] memcg: fix res_counter_read_u64 lock aware (Was " KAMEZAWA Hiroyuki
2011-01-27 1:08 ` Andrew Morton
2011-01-27 1:24 ` KAMEZAWA Hiroyuki [this message]
2011-01-27 1:34 ` KAMEZAWA Hiroyuki
2011-01-27 1:55 ` Andrew Morton
2011-01-27 1:43 ` [BUGFIX v2] " KAMEZAWA Hiroyuki
2011-01-27 1:57 ` Andrew Morton
2011-01-27 2:13 ` KAMEZAWA Hiroyuki
2011-01-27 0:40 ` KAMEZAWA Hiroyuki
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=20110127102418.fc200c96.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.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