[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1091a91e-f8ee-b091-6d95-78b33520fb2d@oracle.com>
Date: Fri, 23 Mar 2018 14:41:29 -0700
From: NAGARATHNAM MUTHUSAMY <nagarathnam.muthusamy@...cle.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Linux Containers <containers@...ts.linux-foundation.org>,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
khlebnikov@...dex-team.ru, prakash.sangappa@...cle.com,
luto@...nel.org, akpm@...ux-foundation.org, oleg@...hat.com,
serge.hallyn@...ntu.com, esyr@...hat.com, jannh@...gle.com,
linux-security-module@...r.kernel.org,
Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [REVIEW][PATCH 09/11] ipc/shm: Fix shmctl(..., IPC_STAT, ...)
between pid namespaces.
On 3/23/2018 2:33 PM, ebiederm@...ssion.com wrote:
> NAGARATHNAM MUTHUSAMY <nagarathnam.muthusamy@...cle.com> writes:
>
>> Thanks!
>>
>> Reviewed-by: Nagarathnam Muthusamy <nagarathnam.muthusamy@...cle.com>
> Does this look like it will address the issue you have been fighting
> with pids?
We do use IPC shared memory but it is a single large one, shared by multiple
levels. We are currently looking into using a similar solution based on
file locks.
When a new level is created, a file representing that level could be
created in
a common path which could be locked by the init process of that level.
Parent levels could query the locking pid of that file to get the pid
translation
of the init process of the required level. Then it could open a file
descriptor
and use the translate_pid API for further translations.
Thanks,
Nagarathnam.
>
> Eric
Powered by blists - more mailing lists