From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: xt_recent broken in kernel 3.19.0 + PATCH
Date: Wed, 11 Feb 2015 18:31:21 +0000 [thread overview]
Message-ID: <20150211183121.6688aec8@bother.homenet> (raw)
In-Reply-To: <20150211092834.65f8ae80@bother.homenet>
On Wed, 11 Feb 2015 09:28:34 +0000
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> With kernel 3.19.0, the following iptables rule, where SSH_TRIES is
> set to 4:
>
> iptables -D SSH_CHAIN -m conntrack --ctstate NEW \
> -m recent --update --seconds $SSH_LOGIN_PERIOD --hitcount
> $SSH_TRIES -j DROP
>
> generates this error message in syslog:
>
> kernel: xt_recent: hitcount (4) is larger than packets to be
> remembered (4) for table DEFAULT
>
> and the rule fails to install in the table. No error is generated
> with kernel 3.18.6.
The rule provoking this should of course have been the one appending
the rule, which is:
iptables -A SSH_CHAIN -m conntrack --ctstate NEW \
-m recent --update --seconds $SSH_LOGIN_PERIOD --hitcount $SSH_TRIES -j DROP
On looking at the code, the changes in the 3.19 kernel seem not to have
been tested and there is an off-by-one error. The patch below restores
behaviour to be identical to that found in the 3.18 kernel.
Chris
--- linux-3.19.0/net/netfilter/xt_recent.c~ 2015-02-10 09:18:44.657376355 +0000
+++ linux-3.19.0/net/netfilter/xt_recent.c 2015-02-11 17:58:33.311608835 +0000
@@ -378,7 +378,7 @@
mutex_lock(&recent_mutex);
t = recent_table_lookup(recent_net, info->name);
if (t != NULL) {
- if (info->hit_count > t->nstamps_max_mask) {
+ if (info->hit_count > t->nstamps_max_mask + 1) {
pr_info("hitcount (%u) is larger than packets to be remembered (%u) for table %s\n",
info->hit_count, t->nstamps_max_mask + 1,
info->name);
next prev parent reply other threads:[~2015-02-11 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 9:28 xt_recent broken in kernel 3.19.0 Chris Vine
2015-02-11 18:31 ` Chris Vine [this message]
2015-02-12 3:15 ` xt_recent broken in kernel 3.19.0 + PATCH Cong Wang
2015-02-12 8:35 ` Florian Westphal
2015-02-12 10:26 ` Chris Vine
2015-02-12 10:54 ` Chris Vine
2015-02-12 11:11 ` Chris Vine
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=20150211183121.6688aec8@bother.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®