Thread (14 messages) 14 messages, 7 authors, 2012-01-21

Re: [PATCH 3/3] memcg: let css_get_next() rely upon rcu_read_lock()

From: Tejun Heo <hidden>
Date: 2012-01-19 20:54:02
Also in: linux-mm, lkml

On Thu, Jan 19, 2012 at 12:51:47PM -0800, Hugh Dickins wrote:
Remove lock and unlock around css_get_next()'s call to idr_get_next().
memcg iterators (only users of css_get_next) already did rcu_read_lock(),
and its comment demands that; but add a WARN_ON_ONCE to make sure of it.

Signed-off-by: Hugh Dickins <redacted>
Acked-by: KAMEZAWA Hiroyuki <redacted>
Acked-by: Li Zefan <redacted>
All three look good to me,

 Acked-by: Tejun Heo [off-list ref]

Thanks.

-- 
tejun
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help