From: Samuel Jean <sj-netfilter@cookinglinux.org>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: [PATCH] ipt_hashlimit.c: expire's type overflow when showing tuples at bad moment.
Date: Sat, 22 Jan 2005 20:32:02 -0500 [thread overview]
Message-ID: <41F2FE92.6020603@cookinglinux.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Name: Expire's type overflow when showing tuples at bad moment.
Status: Tested under Linux 2.6.6 uml patched.
Signed-off-by: Samuel Jean <sjean@cookinglinux.org>
When garbage collector runs slow enough, we have a chance to print
expired tuples before they get freed. We see weird expiry time.
Not sure if I needed 'now' reference so I didn't took chance.
Index: linux-2.6.6/net/ipv4/netfilter/ipt_hashlimit.c
===================================================================
[-- Attachment #2: ipt_hashlimit.c-proc_show.patch --]
[-- Type: text/x-patch, Size: 840 bytes --]
--- net/ipv4/netfilter/ipt_hashlimit.c.orig 2005-01-22 19:48:05.000000000 -0500
+++ net/ipv4/netfilter/ipt_hashlimit.c 2005-01-22 19:50:44.000000000 -0500
@@ -605,11 +605,12 @@ static void dl_seq_stop(struct seq_file
static inline int dl_seq_real_show(struct dsthash_ent *ent, struct seq_file *s)
{
+ unsigned int now = jiffies;
/* recalculate to show accurate numbers */
- rateinfo_recalc(ent, jiffies);
+ rateinfo_recalc(ent, now);
- return seq_printf(s, "%ld %u.%u.%u.%u:%u->%u.%u.%u.%u:%u %u %u %u\n",
- (ent->expires - jiffies)/HZ,
+ return seq_printf(s, "%lu %u.%u.%u.%u:%u->%u.%u.%u.%u:%u %u %u %u\n",
+ (ent->expires > now) ? (ent->expires - now)/HZ : 0,
NIPQUAD(ent->dst.src_ip), ntohs(ent->dst.src_port),
NIPQUAD(ent->dst.dst_ip), ntohs(ent->dst.dst_port),
ent->rateinfo.credit, ent->rateinfo.credit_cap,
next reply other threads:[~2005-01-23 1:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 1:32 Samuel Jean [this message]
2005-02-01 13:29 ` [PATCH] ipt_hashlimit.c: expire's type overflow when showing tuples at bad moment Harald Welte
2005-02-01 13:43 ` Patrick McHardy
2005-02-01 13:54 ` Harald Welte
2005-02-01 14:20 ` Patrick McHardy
2005-02-01 14:53 ` Samuel Jean
2005-02-01 18:16 ` Patrick McHardy
2005-02-01 21:47 ` Samuel Jean
2005-02-02 2:11 ` 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=41F2FE92.6020603@cookinglinux.org \
--to=sj-netfilter@cookinglinux.org \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.