From: "David S. Miller" <davem@redhat.com>
To: Wensong Zhang <wensong@linux-vs.org>
Cc: netdev@oss.sgi.com, ja@ssi.bg
Subject: Re: [2.6 PATCH] Fix IPVS sync state check
Date: Mon, 13 Oct 2003 12:25:40 -0700 [thread overview]
Message-ID: <20031013122540.0446f173.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310132306490.1216-200000@penguin.linux-vs.org>
On Mon, 13 Oct 2003 23:15:26 +0800 (CST)
Wensong Zhang <wensong@linux-vs.org> wrote:
> Here is a one-line fix in the sync state check for the connection to be
> synchronized. Since both the primay and the backup IPVS sync daemon can be
> started in a box at a time now, we must check if the MASTER bit is set in
> the sync state exactly.
>
> Please check and apply it.
Looks good, applied. Thanks.
BTW, on the 2.4.x side the IPVS code still has the NF_DROP return
which Julian changed in the 2.6.x version of the IPVS code. Maybe
this 2.6.x NF_DROP change needs to be propagated into the 2.4.x code?
next prev parent reply other threads:[~2003-10-13 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 15:15 [2.6 PATCH] Fix IPVS sync state check Wensong Zhang
2003-10-13 19:25 ` David S. Miller [this message]
2003-10-13 21:29 ` Julian Anastasov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031013122540.0446f173.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.com \
--cc=wensong@linux-vs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).