Re: [PATCH v2 0/5] ipvs: fix backup sync daemon with IPv6, and minor updates

2016-06-15 Thread Julian Anastasov
Hello, On Wed, 15 Jun 2016, Quentin Armitage wrote: > I am updating the patches in line with your comments, but I'm not sure about > a couple of points. > > Patch 4: > > You state that before bind(), such changes should be safe. However, from the > function make_send_sock(), when the

Re: [PATCH v2 0/5] ipvs: fix backup sync daemon with IPv6, and minor updates

2016-06-15 Thread Julian Anastasov
Hello, On Wed, 15 Jun 2016, Quentin Armitage wrote: > I am updating the patches in line with your comments, but I'm not sure about > a couple of points. > > Patch 4: > > You state that before bind(), such changes should be safe. However, from the > function make_send_sock(), when the

Re: [PATCH v2 0/5] ipvs: fix backup sync daemon with IPv6, and minor updates

2016-06-14 Thread Julian Anastasov
Hello, On Tue, 14 Jun 2016, Quentin Armitage wrote: > This series of patches arise from discovering that: > ipvsadm --start-daemon backup --mcast-group IPv6_address ... > would always fail. > > The first patch resolves the problem. The second and third patches are > optimizations that

Re: [PATCH v2 0/5] ipvs: fix backup sync daemon with IPv6, and minor updates

2016-06-14 Thread Julian Anastasov
Hello, On Tue, 14 Jun 2016, Quentin Armitage wrote: > This series of patches arise from discovering that: > ipvsadm --start-daemon backup --mcast-group IPv6_address ... > would always fail. > > The first patch resolves the problem. The second and third patches are > optimizations that