From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: [RFC] Payloads and transient filesystem support for user-cr Date: Wed, 02 Mar 2011 16:23:17 -0800 Message-ID: <877hch6oi2.fsf@caffeine.danplanet.com> References: <1299101725-17603-1-git-send-email-danms@us.ibm.com> <4D6EBF24.4000601@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org List-Id: containers.vger.kernel.org DL> The posix semaphore use the mapped deleted hardlinked files. DL> AFAIK, the current implementation do not support that, no ? DL> How is it possible to CR programs using sem_* operations in this case ? You're right. This addresses the problem of /dev/shm/sem.foo going away when the container's /dev/shm mount is destroyed. It does not address the fact that the mmap()'d unlinked file is restored as an anonymous region and therefore becomes disjoint with the one on-disk. I expect the evolution of the unlinked files patches will resolve that. Our naive tests are not discriminating enough to make this distinction at the moment, which certainly needs to be resolved :) -- Dan Smith IBM Linux Technology Center email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org