er other class devices.
To avoid breaking userland, a tapNN symlink pointing to macvtap/tapNN is
created inside the macvtapX directory.
Signed-off-by: Marc Angel
---
drivers/net/macvtap.c | 36 ++--
1 file changed, 26 insertions(+), 10 deletions(-)
diff --git a/d
On Thu, May 5, 2016 at 4:53 AM, David Miller wrote:
> From: Marc Angel
> Date: Thu, 5 May 2016 01:33:09 +0100
>
>> On Wed, May 4, 2016 at 9:04 PM, David Miller wrote:
>>> From: Marc Angel
>>> Date: Tue, 3 May 2016 20:30:54 +0200
>>>
>>>>
On Wed, May 4, 2016 at 9:04 PM, David Miller wrote:
> From: Marc Angel
> Date: Tue, 3 May 2016 20:30:54 +0200
>
>> @@ -1274,6 +1285,7 @@ static int macvtap_device_event(struct notifier_block
>> *unused,
>> unsigned long event, void
er other class devices.
To avoid breaking userland, a tapNN symlink pointing to macvtap/tapNN is
created inside the macvtapX directory.
Signed-off-by: Marc Angel
---
drivers/net/macvtap.c | 36 ++--
1 file changed, 26 insertions(+), 10 deletions(-)
diff --git a/d
er other class devices.
To avoid breaking userland, a tapNN symlink pointing to macvtap/tapNN is
created inside the macvtapX directory.
Signed-off-by: Marc Angel
---
drivers/net/macvtap.c | 35 +--
1 file changed, 25 insertions(+), 10 deletions(-)
diff --git a/drive
On Mon, Apr 25, 2016 at 8:12 PM, Eric W. Biederman
wrote:
>> The 'net' device class is isolated between network namespaces so each
>> one has its own hierarchy of net devices.
>> This isn't the case for the 'macvtap' device class.
>> The problem occurs half-way through the netdev registration, whe
irtual/net/macvtapX/macvtap/tapNN
This is due to Commit 24b1442 ("Driver-core: Always create class
directories for classses that support namespaces.")
Signed-off-by: Marc Angel
---
I'm not sure that the problems described in that commit message
apply to macvtaps so maybe it is possi
