Dmitry Torokhov writes:
> On Mon, Aug 29, 2016 at 5:38 AM, Eric W. Biederman
> wrote:
>> David Miller writes:
>>
>>> From: Dmitry Torokhov
>>> Date: Tue, 16 Aug 2016 15:33:10 -0700
>>>
There
On Mon, Aug 29, 2016 at 5:38 AM, Eric W. Biederman
wrote:
> David Miller writes:
>
>> From: Dmitry Torokhov
>> Date: Tue, 16 Aug 2016 15:33:10 -0700
>>
>>> There are objects in /sys hierarchy (/sys/class/net/) that logically
David Miller writes:
> From: Dmitry Torokhov
> Date: Tue, 16 Aug 2016 15:33:10 -0700
>
>> There are objects in /sys hierarchy (/sys/class/net/) that logically belong
>> to a namespace/container. Unfortunately all sysfs objects start their life
>>
On Sun, Aug 21, 2016 at 11:41:39PM -0700, David Miller wrote:
> From: Dmitry Torokhov
> Date: Tue, 16 Aug 2016 15:33:10 -0700
>
> > There are objects in /sys hierarchy (/sys/class/net/) that logically belong
> > to a namespace/container. Unfortunately all sysfs objects
From: Dmitry Torokhov
Date: Tue, 16 Aug 2016 15:33:10 -0700
> There are objects in /sys hierarchy (/sys/class/net/) that logically belong
> to a namespace/container. Unfortunately all sysfs objects start their life
> belonging to global root, and while we could change
From: Dmitry Torokhov
Date: Tue, 16 Aug 2016 15:33:10 -0700
> There are objects in /sys hierarchy (/sys/class/net/) that logically belong
> to a namespace/container. Unfortunately all sysfs objects start their life
> belonging to global root, and while we could change
There are objects in /sys hierarchy (/sys/class/net/) that logically belong
to a namespace/container. Unfortunately all sysfs objects start their life
belonging to global root, and while we could change ownership manually,
keeping tracks of all objects that come and go is cumbersome. It would
be