[IPVS]: Don't leak sysctl tables if the scheduler registration fails.
authorPavel Emelyanov <xemul@openvz.org>
Tue, 4 Dec 2007 08:43:24 +0000 (00:43 -0800)
committerDavid S. Miller <davem@sunset.davemloft.net>
Wed, 5 Dec 2007 13:37:26 +0000 (05:37 -0800)
commita014bc8f0f0a3a0cac4fef656f101cdfb77b71eb
tree0b48fdff5525ddba1c64a8c0fd8c8fb6e1a9aeab
parente3c0ac04f980750a368f7cd5f1b8d1d2cdc1f735
[IPVS]: Don't leak sysctl tables if the scheduler registration fails.

In case we load lblc or lblcr module we can leak some sysctl
tables if the call to register_ip_vs_scheduler() fails.

I've looked at the register_ip_vs_scheduler() code and saw, that
the only reason to fail is the name collision, so I think that
with some 3rd party schedulers this becomes a relevant issue. No?

Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Acked-by: Simon Horman <horms@verge.net.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/ipvs/ip_vs_lblc.c
net/ipv4/ipvs/ip_vs_lblcr.c