Hi Pavel,

All three patches look perfectly fine to me.
Feel free to add Acked-by: Max Krasnyansky <maxk@qualcomm.com>

Pavel Emelyanov wrote:
quoted text
> This is basically means that a net is set for a new device, but
> actually this involves two more steps:
> 
> 1. mark the tun device as "local", i.e. do not allow for it to
>    move across namespaces.
> 
> This is done so, since tun device is most often associated to some
> file (and thus to some process) and moving the device alone is not
> valid while keeping the file and the process outside.
> 
> 2. get the tun device's net when tun becomes attached and put one
>    when it becomes detached.
> 
> This is needed to handle the case when a task owning the tun dies,
> but a files lives for some more time - in this case we must not
> allow for net to be freed, since its exit hook will spoil that file's
> private data by unregistering the tun from under tun_chr_close.
I'm not sure what you mean "by file lives on" here. I believe you're talking 
about persistent tun devices. ie Those that exist in detached state and are 
not attached to any file descriptors.
"net" refcounting logic there looks fine to me.

Max


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html