* [PATCH][NETFILTER]: Fix race between clusterip_config_find_get and _entry_put.
@ 2008-04-12 10:44 Pavel Emelyanov
2008-04-13 4:55 ` Patrick McHardy
0 siblings, 1 reply; 2+ messages in thread
From: Pavel Emelyanov @ 2008-04-12 10:44 UTC (permalink / raw)
To: Patrick McHardy; +Cc: Linux Netdev List, David Miller
Consider we are putting a clusterip_config entry with the "entries"
count == 1, and on the other CPU there's a clusterip_config_find_get
in progress:
CPU1: CPU2:
clusterip_config_entry_put: clusterip_config_find_get:
if (atomic_dec_and_test(&c->entries)) {
/* true */
read_lock_bh(&clusterip_lock);
c = __clusterip_config_find(clusterip);
/* found - it's still in list */
...
atomic_inc(&c->entries);
read_unlock_bh(&clusterip_lock);
write_lock_bh(&clusterip_lock);
list_del(&c->list);
write_unlock_bh(&clusterip_lock);
...
dev_put(c->dev);
Oops! We have an entry returned by the clusterip_config_find_get,
which is a) not in list b) has a stale dev pointer.
The problems will happen when the CPU2 will release the entry - it
will remove it from the list for the 2nd time, thus spoiling it, and
will put a stale dev pointer.
The fix is to make atomic_dec_and_test under the clusterip_lock.
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
---
diff --git a/net/ipv4/netfilter/ipt_CLUSTERIP.c b/net/ipv4/netfilter/ipt_CLUSTERIP.c
index 52926c8..a12dd32 100644
--- a/net/ipv4/netfilter/ipt_CLUSTERIP.c
+++ b/net/ipv4/netfilter/ipt_CLUSTERIP.c
@@ -82,8 +82,8 @@ clusterip_config_put(struct clusterip_config *c)
static inline void
clusterip_config_entry_put(struct clusterip_config *c)
{
+ write_lock_bh(&clusterip_lock);
if (atomic_dec_and_test(&c->entries)) {
- write_lock_bh(&clusterip_lock);
list_del(&c->list);
write_unlock_bh(&clusterip_lock);
@@ -96,7 +96,9 @@ clusterip_config_entry_put(struct clusterip_config *c)
#ifdef CONFIG_PROC_FS
remove_proc_entry(c->pde->name, c->pde->parent);
#endif
+ return;
}
+ write_unlock_bh(&clusterip_lock);
}
static struct clusterip_config *
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH][NETFILTER]: Fix race between clusterip_config_find_get and _entry_put.
2008-04-12 10:44 [PATCH][NETFILTER]: Fix race between clusterip_config_find_get and _entry_put Pavel Emelyanov
@ 2008-04-13 4:55 ` Patrick McHardy
0 siblings, 0 replies; 2+ messages in thread
From: Patrick McHardy @ 2008-04-13 4:55 UTC (permalink / raw)
To: Pavel Emelyanov
Cc: Linux Netdev List, David Miller,
Netfilter Development Mailinglist
[Please remeber to CC netfilter-devel]
Pavel Emelyanov wrote:
> Consider we are putting a clusterip_config entry with the "entries"
> count == 1, and on the other CPU there's a clusterip_config_find_get
> in progress:
>
> CPU1: CPU2:
> clusterip_config_entry_put: clusterip_config_find_get:
> if (atomic_dec_and_test(&c->entries)) {
> /* true */
> read_lock_bh(&clusterip_lock);
> c = __clusterip_config_find(clusterip);
> /* found - it's still in list */
> ...
> atomic_inc(&c->entries);
> read_unlock_bh(&clusterip_lock);
>
> write_lock_bh(&clusterip_lock);
> list_del(&c->list);
> write_unlock_bh(&clusterip_lock);
> ...
> dev_put(c->dev);
>
> Oops! We have an entry returned by the clusterip_config_find_get,
> which is a) not in list b) has a stale dev pointer.
>
> The problems will happen when the CPU2 will release the entry - it
> will remove it from the list for the 2nd time, thus spoiling it, and
> will put a stale dev pointer.
>
> The fix is to make atomic_dec_and_test under the clusterip_lock.
I guess an alternative would have been to use atomic_inc_not_zero
in clusterip_config_find_get. But this is only called very rarely,
so it doesn't really matter.
Applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-04-13 4:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-12 10:44 [PATCH][NETFILTER]: Fix race between clusterip_config_find_get and _entry_put Pavel Emelyanov
2008-04-13 4:55 ` Patrick McHardy
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).