OpenVZ Forum


Home » Mailing lists » Devel » Re: Containers: css_put() dilemma
Re: Containers: css_put() dilemma [message #19360] Tue, 17 July 2007 07:18 Go to previous message
Paul Menage is currently offline  Paul Menage
Messages: 642
Registered: September 2006
Senior Member
On 7/17/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >
> > >                mutex_lock(&container_mutex);
> > >                set_bit(CONT_RELEASABLE, &cont->flags);
> > >-               if (atomic_dec_and_test(&css->refcnt)) {
> > >-                       check_for_release(cont);
> > >-               }
> > >+               check_for_release(cont);
> > >                mutex_unlock(&container_mutex);
> > >

I think that this isn't safe as it stands, without a synchronize_rcu()
in container_diput() prior to the kfree(). Also, it will break if
anyone tries to use a release agent on a hierarchy that has your
memory controller bound to it.

Paul
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Previous Topic: [PATCH] Fix user struct leakage with locked IPC shem segment
Next Topic: [PATCH] SLAB_PANIC more (proc, posix-timers, shmem)
Goto Forum:
  


Current Time: Thu Jul 24 02:39:17 GMT 2025

Total time taken to generate the page: 0.15362 seconds