Re: [PATCH net-next] tun: Do SIOCGSKNS out of rtnl_lock()

2018-05-10 Thread David Miller
From: Kirill Tkhai Date: Tue, 08 May 2018 19:21:34 +0300 > Since net ns of tun device is assigned on the device creation, > and it never changes, we do not need to use any lock to get it > from alive tun. > > Signed-off-by: Kirill Tkhai Applied, thank you.

Re: [PATCH net-next] tun: Do SIOCGSKNS out of rtnl_lock()

2018-05-09 Thread Jason Wang
On 2018年05月09日 17:00, Kirill Tkhai wrote: Hi, Jason, On 09.05.2018 10:18, Jason Wang wrote: On 2018年05月09日 00:21, Kirill Tkhai wrote: Since net ns of tun device is assigned on the device creation, and it never changes, we do not need to use any lock to get it from alive tun. Signed-off-by:

Re: [PATCH net-next] tun: Do SIOCGSKNS out of rtnl_lock()

2018-05-09 Thread Kirill Tkhai
Hi, Jason, On 09.05.2018 10:18, Jason Wang wrote: > > > On 2018年05月09日 00:21, Kirill Tkhai wrote: >> Since net ns of tun device is assigned on the device creation, >> and it never changes, we do not need to use any lock to get it >> from alive tun. >> >> Signed-off-by: Kirill Tkhai >> --- >>  

Re: [PATCH net-next] tun: Do SIOCGSKNS out of rtnl_lock()

2018-05-09 Thread Jason Wang
On 2018年05月09日 00:21, Kirill Tkhai wrote: Since net ns of tun device is assigned on the device creation, and it never changes, we do not need to use any lock to get it from alive tun. Signed-off-by: Kirill Tkhai --- drivers/net/tun.c | 18 +++--- 1 file changed, 7 insertions(

[PATCH net-next] tun: Do SIOCGSKNS out of rtnl_lock()

2018-05-08 Thread Kirill Tkhai
Since net ns of tun device is assigned on the device creation, and it never changes, we do not need to use any lock to get it from alive tun. Signed-off-by: Kirill Tkhai --- drivers/net/tun.c | 18 +++--- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/drivers/net/tu