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,
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
(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
(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
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
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
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
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
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
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
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
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,
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
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:
>
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
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,
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 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:
>
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
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
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
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
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/
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,
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,
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
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
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
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
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
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
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
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
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
34 matches
Mail list logo