From: Patrick McHardy <kaber@trash.net>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
Cc: Thomas Jarosch <thomas.jarosch@intra2net.com>,
netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: [patch] Fix ipt_ACCOUNT for large networks - 2nd try
Date: Sun, 24 Apr 2005 18:54:35 +0200 [thread overview]
Message-ID: <426BCF4B.7030500@trash.net> (raw)
In-Reply-To: <425F0053.2050302@gmx.net>
Carl-Daniel Hailfinger wrote:
>>diff -u -r -b ACCOUNT/linux/net/ipv4/netfilter/ipt_ACCOUNT.c ACCOUNT.1.4/linux/net/ipv4/netfilter/ipt_ACCOUNT.c
>>--- ACCOUNT/linux/net/ipv4/netfilter/ipt_ACCOUNT.c 2004-06-13 22:41:21.000000000 +0200
>>+++ ACCOUNT.1.4/linux/net/ipv4/netfilter/ipt_ACCOUNT.c 2005-04-05 09:33:52.000000000 +0200
>>@@ -694,7 +694,8 @@
>> /* Copy 8 bit network data into a prepared buffer.
>> We only copy entries != 0 to increase performance.
>> */
>>-static int ipt_acc_handle_copy_data(void *to_user, int *pos,
>>+static int ipt_acc_handle_copy_data(void *to_user, u_int32_t *to_user_pos,
>>+ u_int32_t *tmpbuf_pos,
>> struct ipt_acc_mask_24 *data,
>> u_int32_t net_ip, u_int32_t net_OR_mask)
>> {
>
>
> You seem to like u_int32_t as a type. That causes interesting behaviour
> on 64bit machines. Is there any design objective dictating that?
> I have a patch available changing most occurences of u_int32_t to
> something more generic (of course not for IPs, netmasks and such) which
> may make sense if you ever want to use your module on 64bit machines.
Seems to be fine, AFAICT the u_int32_ts are only used as offsets.
Regards
Patrick
next prev parent reply other threads:[~2005-04-24 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 7:48 [patch] Fix ipt_ACCOUNT for large networks - 2nd try Thomas Jarosch
2005-04-11 13:30 ` Carl-Daniel Hailfinger
2005-04-11 18:13 ` Thomas Jarosch
2005-04-14 23:44 ` Carl-Daniel Hailfinger
2005-04-15 8:29 ` Thomas Jarosch
2005-04-24 16:54 ` Patrick McHardy [this message]
2005-04-24 16:52 ` Patrick McHardy
2005-04-24 17:06 ` Thomas Jarosch
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=426BCF4B.7030500@trash.net \
--to=kaber@trash.net \
--cc=c-d.hailfinger.devel.2005@gmx.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=thomas.jarosch@intra2net.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 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.