All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Grebe <josh@brokedown.net>
To: sparclinux@vger.kernel.org
Subject: Re: 2.4 kernels and max # of rules with iptables
Date: Wed, 17 Aug 2005 13:06:06 +0000	[thread overview]
Message-ID: <4303363E.80503@brokedown.net> (raw)
In-Reply-To: <20050619200712.036920e1@enterprise.weeve.org>

Good Morning,

I threw a little printk patch at Jason and we determined that to be 
correct. In do_netfilter_replace(), on about line 2924, the call
        krepl = (struct ipt_replace *)kmalloc(kreplsize, GFP_KERNEL);
results in krepl being NULL after a pile of rules have been added.

I compiled a statically linked iptables binary and Jason was able to 
add over 7k rules before he stopped it, the 32 bit iptables bombs 
before 900 rules.

As far as changing this behaviour, I plead ignorance.

Thanks,

Josh


Jason Wever wrote:
> On Sun, 19 Jun 2005 19:20:34 -0700 (PDT)
> "David S. Miller" <davem@davemloft.net> wrote:
> 
> 
>>64-bit or 32-bit userland binaries?
> 
> 
> 32 bit userland binaries.  Currently we don't have a working 64 bit
> environment that is suggested for general use.
>  
> 
>>He could be hitting the kmalloc() limit via the netfilter
>>32-bit userland compat code in:
>>
>>       arch/sparc64/kernel/sys_sparc32.c:do_netfilter_replace()
>>

  parent reply	other threads:[~2005-08-17 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20  2:07 2.4 kernels and max # of rules with iptables Jason Wever
2005-06-20  2:20 ` David S. Miller
2005-06-20  2:27 ` Jason Wever
2005-06-22  2:25 ` Jason Wever
2005-08-17 13:06 ` Josh Grebe [this message]
2005-08-17 18:33 ` David S. Miller
2005-08-17 18:53 ` Josh Grebe
2005-08-17 18:57 ` David S. Miller
2005-08-22 17:10 ` Gustavo Zacarias
2005-08-22 17:14 ` David S. Miller
2005-08-22 17:17 ` Gustavo Zacarias

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=4303363E.80503@brokedown.net \
    --to=josh@brokedown.net \
    --cc=sparclinux@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 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.