netfilter: xt_recent: fix regression in rules using a zero hit_count
authorPatrick McHardy <kaber@trash.net>
Mon, 22 Mar 2010 17:25:20 +0000 (18:25 +0100)
committerPatrick McHardy <kaber@trash.net>
Mon, 22 Mar 2010 17:25:20 +0000 (18:25 +0100)
commitef1691504c83ba3eb636c0cfd3ed33f7a6d0b4ee
tree7eac65d59454eb5d4f8b1495f3977d6ac0113364
parent220bf991b0366cc50a94feede3d7341fa5710ee4
netfilter: xt_recent: fix regression in rules using a zero hit_count

Commit 8ccb92ad (netfilter: xt_recent: fix false match) fixed supposedly
false matches in rules using a zero hit_count. As it turns out there is
nothing false about these matches and people are actually using entries
with a hit_count of zero to make rules dependant on addresses inserted
manually through /proc.

Since this slipped past the eyes of three reviewers, instead of
reverting the commit in question, this patch explicitly checks
for a hit_count of zero to make the intentions more clear.

Reported-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
Tested-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: stable@kernel.org
Signed-off-by: Patrick McHardy <kaber@trash.net>
net/netfilter/xt_recent.c