ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds
authorSabrina Dubroca <sd@queasysnail.net>
Tue, 5 Jun 2018 13:01:59 +0000 (15:01 +0200)
committerDavid S. Miller <davem@davemloft.net>
Tue, 5 Jun 2018 16:26:39 +0000 (12:26 -0400)
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 commit 5e1859fbcc3c ("ipv4: ipmr:
various fixes and cleanups").

Fixes: d1db275dd3f6 ("ipv6: ip6mr: support multiple tables")
Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv6/ip6mr.c

index 20a419ee800057a4fb6ad4c66ff7bf71dff44d3a..5c57374850b306052289a8732b5a25bf8bfa9e9d 100644 (file)
@@ -1760,7 +1760,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;
        }