Re: [RESEND RFC] translate_pid API

2018-03-20 Thread Eric W. Biederman
Nagarathnam Muthusamy writes: > (Resending the reply as there was a reject due to HTML in email) > > On 03/14/2018 03:03 PM, ebied...@xmission.com wrote: >> Nagarathnam Muthusamy writes: >> >>> On 03/13/2018 08:29 PM,

Re: [RESEND RFC] translate_pid API

2018-03-20 Thread Eric W. Biederman
Nagarathnam Muthusamy writes: > (Resending the reply as there was a reject due to HTML in email) > > On 03/14/2018 03:03 PM, ebied...@xmission.com wrote: >> Nagarathnam Muthusamy writes: >> >>> On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: The cost of that ``cheaper'' u64 that is

Re: [RESEND RFC] translate_pid API

2018-03-20 Thread Nagarathnam Muthusamy
(Resending the reply as there was a reject due to HTML in email) On 03/14/2018 03:03 PM, ebied...@xmission.com wrote: Nagarathnam Muthusamy writes: On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: The cost of that ``cheaper'' u64 that is not in any

Re: [RESEND RFC] translate_pid API

2018-03-20 Thread Nagarathnam Muthusamy
(Resending the reply as there was a reject due to HTML in email) On 03/14/2018 03:03 PM, ebied...@xmission.com wrote: Nagarathnam Muthusamy writes: On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: The cost of that ``cheaper'' u64 that is not in any namespace is that you now have to go

Re: [RESEND RFC] translate_pid API

2018-03-14 Thread Eric W. Biederman
Nagarathnam Muthusamy writes: > On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: >> The cost of that ``cheaper'' u64 that is not in any namespace is that >> you now have to go and implement a namespace of namespaces. You haven't >> even attempted it. So

Re: [RESEND RFC] translate_pid API

2018-03-14 Thread Eric W. Biederman
Nagarathnam Muthusamy writes: > On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: >> The cost of that ``cheaper'' u64 that is not in any namespace is that >> you now have to go and implement a namespace of namespaces. You haven't >> even attempted it. So just no.Anything that brings us

Re: [RESEND RFC] translate_pid API

2018-03-14 Thread Nagarathnam Muthusamy
On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: nagarathnam.muthus...@oracle.com writes: Resending the RFC with participants of previous discussions in the list. Nacked-by: "Eric W. Biederman" Please read below to see why. Following patch which is a variation

Re: [RESEND RFC] translate_pid API

2018-03-14 Thread Nagarathnam Muthusamy
On 03/13/2018 08:29 PM, ebied...@xmission.com wrote: nagarathnam.muthus...@oracle.com writes: Resending the RFC with participants of previous discussions in the list. Nacked-by: "Eric W. Biederman" Please read below to see why. Following patch which is a variation of a solution

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Eric W. Biederman
nagarathnam.muthus...@oracle.com writes: > Resending the RFC with participants of previous discussions > in the list. Nacked-by: "Eric W. Biederman" Please read below to see why. > Following patch which is a variation of a solution discussed > in

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Eric W. Biederman
nagarathnam.muthus...@oracle.com writes: > Resending the RFC with participants of previous discussions > in the list. Nacked-by: "Eric W. Biederman" Please read below to see why. > Following patch which is a variation of a solution discussed > in https://lwn.net/Articles/736330/ provides the

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 04:10 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 3:45 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 03:00 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: On 03/13/2018

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 04:10 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 3:45 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 03:00 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM,

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 3:45 PM, Nagarathnam Muthusamy wrote: > On 03/13/2018 03:00 PM, Jann Horn wrote: >> On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy >> wrote: >>> On 03/13/2018 02:28 PM, Jann Horn wrote: On

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 3:45 PM, Nagarathnam Muthusamy wrote: > On 03/13/2018 03:00 PM, Jann Horn wrote: >> On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy >> wrote: >>> On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: >

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 03:00 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: On 03/13/2018

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 03:00 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM,

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: > > > On 03/13/2018 02:28 PM, Jann Horn wrote: >> >> On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy >> wrote: >>> >>> On 03/13/2018 01:47 PM, Jann Horn wrote:

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 2:44 PM, Nagarathnam Muthusamy wrote: > > > On 03/13/2018 02:28 PM, Jann Horn wrote: >> >> On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy >> wrote: >>> >>> On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM, wrote: >

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM, wrote: Resending the RFC with participants

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 02:28 PM, Jann Horn wrote: On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM, wrote: Resending the RFC with participants of previous discussions in the list. Following patch which is a

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: > On 03/13/2018 01:47 PM, Jann Horn wrote: >> On Mon, Mar 12, 2018 at 10:18 AM, >> wrote: >>> >>> Resending the RFC with participants of previous discussions >>> in

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Tue, Mar 13, 2018 at 2:20 PM, Nagarathnam Muthusamy wrote: > On 03/13/2018 01:47 PM, Jann Horn wrote: >> On Mon, Mar 12, 2018 at 10:18 AM, >> wrote: >>> >>> Resending the RFC with participants of previous discussions >>> in the list. >>> >>> Following patch which is a variation of a solution

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM, wrote: Resending the RFC with participants of previous discussions in the list. Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Nagarathnam Muthusamy
On 03/13/2018 01:47 PM, Jann Horn wrote: On Mon, Mar 12, 2018 at 10:18 AM, wrote: Resending the RFC with participants of previous discussions in the list. Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/ provides the users of pid namespace,

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Mon, Mar 12, 2018 at 10:18 AM, wrote: > Resending the RFC with participants of previous discussions > in the list. > > Following patch which is a variation of a solution discussed > in https://lwn.net/Articles/736330/ provides the users of > pid namespace,

Re: [RESEND RFC] translate_pid API

2018-03-13 Thread Jann Horn
On Mon, Mar 12, 2018 at 10:18 AM, wrote: > Resending the RFC with participants of previous discussions > in the list. > > Following patch which is a variation of a solution discussed > in https://lwn.net/Articles/736330/ provides the users of > pid namespace, the functionality of pid translation

[RESEND RFC] translate_pid API

2018-03-12 Thread nagarathnam . muthusamy
Resending the RFC with participants of previous discussions in the list. Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/ provides the users of pid namespace, the functionality of pid translation between namespaces using a namespace identifier. The

[RESEND RFC] translate_pid API

2018-03-12 Thread nagarathnam . muthusamy
Resending the RFC with participants of previous discussions in the list. Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/ provides the users of pid namespace, the functionality of pid translation between namespaces using a namespace identifier. The

Re: [RFC] translate_pid API

2018-03-08 Thread Konstantin Khlebnikov
That's something over-engineered. Instead of keeping all file descriptor you could remember pid of init task and pid-ns inode number for validation. And open pid-ns fd when needed. On 06.03.2018 20:38, nagarathnam.muthus...@oracle.com wrote: Following patch which is a variation of a solution

Re: [RFC] translate_pid API

2018-03-08 Thread Konstantin Khlebnikov
That's something over-engineered. Instead of keeping all file descriptor you could remember pid of init task and pid-ns inode number for validation. And open pid-ns fd when needed. On 06.03.2018 20:38, nagarathnam.muthus...@oracle.com wrote: Following patch which is a variation of a solution

Re: [RFC] translate_pid API

2018-03-08 Thread Nagarathnam Muthusamy
On 03/08/2018 11:51 AM, Konstantin Khlebnikov wrote: That's something over-engineered. Instead of keeping all file descriptor you could remember pid of init task and pid-ns inode number for validation. And open pid-ns fd when needed. This would require keeping track of pid of init task in

Re: [RFC] translate_pid API

2018-03-08 Thread Nagarathnam Muthusamy
On 03/08/2018 11:51 AM, Konstantin Khlebnikov wrote: That's something over-engineered. Instead of keeping all file descriptor you could remember pid of init task and pid-ns inode number for validation. And open pid-ns fd when needed. This would require keeping track of pid of init task in

[RFC] translate_pid API

2018-03-06 Thread nagarathnam . muthusamy
Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/ provides the users of pid namespace, the functionality of pid translation between namespaces using a namespace identifier. The topic of pid translation has been discussed in the community few times but

[RFC] translate_pid API

2018-03-06 Thread nagarathnam . muthusamy
Following patch which is a variation of a solution discussed in https://lwn.net/Articles/736330/ provides the users of pid namespace, the functionality of pid translation between namespaces using a namespace identifier. The topic of pid translation has been discussed in the community few times but