]> err.no Git - linux-2.6/commitdiff
netfilter: ipt_recent: fix race between recent_mt_destroy and proc manipulations
authorPavel Emelyanov <xemul@openvz.org>
Thu, 31 Jul 2008 07:38:31 +0000 (00:38 -0700)
committerDavid S. Miller <davem@davemloft.net>
Thu, 31 Jul 2008 07:38:31 +0000 (00:38 -0700)
The thing is that recent_mt_destroy first flushes the entries
from table with the recent_table_flush and only *after* this
removes the proc file, corresponding to that table.

Thus, if we manage to write to this file the '+XXX' command we
will leak some entries. If we manage to write there a 'clean'
command we'll race in two recent_table_flush flows, since the
recent_mt_destroy calls this outside the recent_lock.

The proper solution as I see it is to remove the proc file first
and then go on with flushing the table. This flushing becomes
safe w/o the lock, since the table is already inaccessible from
the outside.

Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: Patrick McHardy <kaber@trash.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/netfilter/ipt_recent.c

index 21cb053f5d7dbe46b4d8b7aff9da9a6167fcf43d..3974d7cae5c02a05219e712ede460a7091fac964 100644 (file)
@@ -305,10 +305,10 @@ static void recent_mt_destroy(const struct xt_match *match, void *matchinfo)
                spin_lock_bh(&recent_lock);
                list_del(&t->list);
                spin_unlock_bh(&recent_lock);
-               recent_table_flush(t);
 #ifdef CONFIG_PROC_FS
                remove_proc_entry(t->name, proc_dir);
 #endif
+               recent_table_flush(t);
                kfree(t);
        }
        mutex_unlock(&recent_mutex);