From: Simon Horman <horms@verge.net.au>
To: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Cc: Jan Engelhardt <jengelh@medozas.de>,
Stephen Hemminger <shemminger@vyatta.com>,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>, Patrick McHardy <kaber@trash.net>
Subject: Re: [patch v4 10/12] IPVS: Allow configuration of persistence engines
Date: Mon, 4 Oct 2010 22:41:54 +0900 [thread overview]
Message-ID: <20101004134154.GA5469@verge.net.au> (raw)
In-Reply-To: <20101004090818.882956490@akiko.akashicho.tokyo.vergenet.net>
On Mon, Oct 04, 2010 at 06:04:02PM +0900, Simon Horman wrote:
> Allow the persistence engine of a virtual service to be set, edited
> and unset.
>
> This feature only works with the netlink user-space interface.
>
> Signed-off-by: Simon Horman <horms@verge.net.au>
> Acked-by: Julian Anastasov <ja@ssi.bg>
>
> ---
>
> v2
> * Dereference persistence engine when a service is deleted.
> This allows persistence modules to be removed from the kernel
> once they are no longer used.
> * Update for the recent "ipvs: changes related to service usecnt" change
> * Trivial rediff
>
> v4
> * As suggested by Julian Anastasov <ja@ssi.bg>
> - Initialise ip_vs_service_user_kern to zero in ip_vs_copy_usvc_compat()
> to avoid a crash caused by the pe_name element being uninitialised.
*Red Face*
I forgot to test this change and I had made a typo.
I will repost.
next prev parent reply other threads:[~2010-10-04 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 9:03 [patch v4 00/12] IPVS: SIP Persistence Engine Simon Horman
2010-10-04 9:03 ` [patch v4 01/12] netfilter: nf_conntrack_sip: Allow ct_sip_get_header() to be called with a null ct argument Simon Horman
2010-10-04 9:03 ` [patch v4 02/12] netfilter: nf_conntrack_sip: Add callid parser Simon Horman
2010-10-04 9:03 ` [patch v4 03/12] IPVS: compact ip_vs_sched_persist() Simon Horman
2010-10-04 9:03 ` [patch v4 04/12] IPVS: Add struct ip_vs_conn_param Simon Horman
2010-10-04 9:03 ` [patch v4 05/12] IPVS: Allow null argument to ip_vs_scheduler_put() Simon Horman
2010-10-04 9:03 ` [patch v4 06/12] IPVS: ip_vs_{un,}bind_scheduler NULL arguments Simon Horman
2010-10-04 9:03 ` [patch v4 07/12] IPVS: Add struct ip_vs_pe Simon Horman
2010-10-04 9:04 ` [patch v4 08/12] IPVS: Add persistence engine data to /proc/net/ip_vs_conn Simon Horman
2010-10-04 9:04 ` [patch v4 09/12] IPVS: management of persistence engine modules Simon Horman
2010-10-04 9:04 ` [patch v4 10/12] IPVS: Allow configuration of persistence engines Simon Horman
2010-10-04 13:41 ` Simon Horman [this message]
2010-10-04 9:04 ` [patch v4 11/12] IPVS: Fallback if persistence engine fails Simon Horman
2010-10-04 9:04 ` [patch v4 12/12] IPVS: sip persistence engine Simon Horman
2010-10-04 11:30 ` [patch v4 00/12] IPVS: SIP Persistence Engine Simon Horman
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=20101004134154.GA5469@verge.net.au \
--to=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=shemminger@vyatta.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).