[RFC][-mm PATCH 4/8] Memory controller memory accounting (v3)

Paul Menage menage at google.com
Fri Jul 20 14:09:09 PDT 2007

On 7/20/07, Paul Menage <menage at google.com> wrote:
> > +       mem = rcu_dereference(mm->mem_container);
> > +       /*
> > +        * For every charge from the container, increment reference
> > +        * count
> > +        */
> > +       css_get(&mem->css);
> > +       rcu_read_unlock();
> It's not clear to me that this is safe.

Sorry, didn't finish this thought.

Right after the rcu_dereference() the mm could be moved to another
container by some other process.

Since there's an rcu_synchronize() after the movement, and the
rcu_synchronize() caller holds container_mutex then I guess it's not
possible for a third process to delete the container during the RCU
section, since it won't be able to acquire the mutex until after the
RCU read section completes. So OK, it is safe, at least based on the
guarantees made by the current implementation.


More information about the Containers mailing list