ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds
[ Upstream commitpull/10/head848235edb5
] Currently, raw6_sk(sk)->ip6mr_table is set unconditionally during ip6_mroute_setsockopt(MRT6_TABLE). A subsequent attempt at the same setsockopt will fail with -ENOENT, since we haven't actually created that table. A similar fix for ipv4 was included in commit5e1859fbcc
("ipv4: ipmr: various fixes and cleanups"). Fixes:d1db275dd3
("ipv6: ip6mr: support multiple tables") Signed-off-by: Sabrina Dubroca <sd@queasysnail.net> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
parent
cbf561634d
commit
989986db8f
|
@ -1795,7 +1795,8 @@ int ip6_mroute_setsockopt(struct sock *sk, int optname, char __user *optval, uns
|
|||
ret = 0;
|
||||
if (!ip6mr_new_table(net, v))
|
||||
ret = -ENOMEM;
|
||||
raw6_sk(sk)->ip6mr_table = v;
|
||||
else
|
||||
raw6_sk(sk)->ip6mr_table = v;
|
||||
rtnl_unlock();
|
||||
return ret;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue