From: Patrick McHardy <kaber@trash.net>
To: Tim Gardner <timg@tpi.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nf-next: netfilter: xt_recent: Add an entry reaper
Date: Tue, 16 Mar 2010 19:57:44 +0100 [thread overview]
Message-ID: <4B9FD4A8.4070704@trash.net> (raw)
In-Reply-To: <20100316170915.8F49FF88DA@sepang.rtg.net>
Tim Gardner wrote:
>>From f2b0624b159e3282d348cd045741725a64d71716 Mon Sep 17 00:00:00 2001
> From: Tim Gardner <tim.gardner@canonical.com>
> Date: Sat, 27 Feb 2010 20:22:07 -0700
> Subject: [PATCH] netfilter: xt_recent: Add an entry reaper (V4)
>
> One of the problems with the way xt_recent is implemented is that
> there is no efficient way to remove expired entries. Of course,
> one can write a rule '-m recent --remove', but you have to know
> beforehand which entry to delete. This commit adds reaper
> logic which checks the head of the LRU list when a rule
> is invoked that has a '--seconds' value and XT_RECENT_REAP set. If an
> entry ceases to accumulate time stamps, then it will eventually bubble
> to the top of the LRU list where it is then reaped.
Thanks, this looks fine. My only concern is that we currently
don't catch unknown flags, so userspace won't get an error if
the option is used and the kernel doesn't support it. If you
document this clearly we can ignore it this one time, but I'd
appreciate if you could send me a patch on top to check for
unknown flags and refuse them.
> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Applied, thanks.
next prev parent reply other threads:[~2010-03-16 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 17:09 nf-next: netfilter: xt_recent: Add an entry reaper Tim Gardner
2010-03-16 18:57 ` Patrick McHardy [this message]
2010-03-16 19:43 ` Tim Gardner
2010-03-16 20:31 ` Jan Engelhardt
2010-03-16 22:58 ` Tim Gardner
2010-03-16 23:48 ` Jan Engelhardt
2010-03-17 15:19 ` Patrick McHardy
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=4B9FD4A8.4070704@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=timg@tpi.com \
/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;
as well as URLs for NNTP newsgroup(s).