From: Patrick McHardy <kaber@trash.net>
To: Simon Horman <horms@verge.net.au>
Cc: Julian Anastasov <ja@ssi.bg>,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ipvs: changes related to service usecnt
Date: Tue, 21 Sep 2010 18:15:09 +0200 [thread overview]
Message-ID: <4C98DA0D.2000804@trash.net> (raw)
In-Reply-To: <20100919114758.GA18134@verge.net.au>
Am 19.09.2010 13:48, schrieb Simon Horman:
> On Sat, Sep 18, 2010 at 05:18:46PM +0300, Julian Anastasov wrote:
>> >
>> > Change the usage of svc usecnt during command execution:
>> >
>> > - we check if svc is registered but we do not need to hold usecnt
>> > reference while under __ip_vs_mutex, only the packet handling needs
>> > it during scheduling
>> >
>> > - change __ip_vs_service_get to __ip_vs_service_find and
>> > __ip_vs_svc_fwm_get to __ip_vs_svc_fwm_find because now caller
>> > will increase svc->usecnt
>> >
>> > - put common code that calls update_service in __ip_vs_update_dest
>> >
>> > - put common code in ip_vs_unlink_service() and use it to unregister
>> > the service
>> >
>> > - add comment that svc should not be accessed after ip_vs_del_service
>> > anymore
>> >
>> > - all IP_VS_WAIT_WHILE calls are now unified: usecnt > 0
>> >
>> > - Properly log the app ports
>> >
>> > As result, some problems are fixed:
>> >
>> > - possible use-after-free of svc in ip_vs_genl_set_cmd after
>> > ip_vs_del_service because our usecnt reference does not guarantee that
>> > svc is not freed on refcnt==0, eg. when no dests are moved to trash
>> >
>> > - possible usecnt leak in do_ip_vs_set_ctl after ip_vs_del_service
>> > when the service is not freed now, for example, when some
>> > destionations are moved into trash and svc->refcnt remains above 0.
>> > It is harmless because svc is not in hash anymore.
>> >
>> > Signed-off-by: Julian Anastasov <ja@ssi.bg>
> Hi Julian,
>
> thats a pretty big patch to review, but it looks good to me.
Indeed, I'd prefer slightly smaller patches too.
> Acked-by: Simon Horman <horms@verge.net.au>
Applied, thanks.
next prev parent reply other threads:[~2010-09-21 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 14:18 [PATCH] ipvs: changes related to service usecnt Julian Anastasov
2010-09-19 11:48 ` Simon Horman
2010-09-21 16:15 ` Patrick McHardy [this message]
2010-09-20 10:13 ` [RFC][PATCH] ipvs: IPv6 tunnel mode Hans Schillstrom
2010-09-22 13:50 ` Julian Anastasov
2010-09-23 16:16 ` Hans Schillstrom
2010-09-23 22:36 ` Julian Anastasov
2010-09-24 12:06 ` Hans Schillstrom
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=4C98DA0D.2000804@trash.net \
--to=kaber@trash.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.