On Fri, Oct 04, 2019 at 05:45:22PM +0200, Nicolas Dichtel wrote:
> Le 03/10/2019 à 18:19, Guillaume Nault a écrit :
> [snip]
> > Why not using the existing NLM_F_ECHO mechanism?
> >
> > IIUC, if rtnl_net_notifyid() did pass the proper nlmsghdr and portid to
> > rtnl_notify(), the later would autom
Le 03/10/2019 à 18:19, Guillaume Nault a écrit :
[snip]
> Why not using the existing NLM_F_ECHO mechanism?
>
> IIUC, if rtnl_net_notifyid() did pass the proper nlmsghdr and portid to
> rtnl_notify(), the later would automatically notify the caller with
> updated information if the original request
On Wed, Oct 02, 2019 at 10:46:03AM +0200, Nicolas Dichtel wrote:
> Le 02/10/2019 à 03:20, David Miller a écrit :
> > From: Nicolas Dichtel
> > Date: Mon, 30 Sep 2019 18:02:12 +0200
> >
> >> The goal of the series is to ease nsid allocation from userland.
> >> The first patch is a preparation work
From: Nicolas Dichtel
Date: Wed, 2 Oct 2019 10:46:03 +0200
> Is a new flag attribute ok to turn on this reply?
That might work, yes.
Le 02/10/2019 à 03:20, David Miller a écrit :
> From: Nicolas Dichtel
> Date: Mon, 30 Sep 2019 18:02:12 +0200
>
>> The goal of the series is to ease nsid allocation from userland.
>> The first patch is a preparation work and the second enables to receive the
>> new nsid in the answer to RTM_NEWNS
From: Nicolas Dichtel
Date: Mon, 30 Sep 2019 18:02:12 +0200
> The goal of the series is to ease nsid allocation from userland.
> The first patch is a preparation work and the second enables to receive the
> new nsid in the answer to RTM_NEWNSID.
The new reply message could break existing apps.
The goal of the series is to ease nsid allocation from userland.
The first patch is a preparation work and the second enables to receive the
new nsid in the answer to RTM_NEWNSID.
net/core/net_namespace.c | 118 ---
1 file changed, 71 insertions(+), 4
