From: Leo Cavaille <chiron@via.ecp.fr>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: [iptables] Implement huge amount of iptables make system crash
Date: Mon, 5 Dec 2011 01:07:58 +0100 [thread overview]
Message-ID: <20111205000758.GA25556@via.ecp.fr> (raw)
In-Reply-To: <alpine.LNX.2.01.1112042207270.5627@frira.zrqbmnf.qr>
Le Sun, Dec 04, 2011 at 10:09:07PM +0100, Jan Engelhardt a écrit :
> >2) These ~62k rules are not really significant for the load of my
> >firewall. But unfortunately, I had sometimes in my tests to manage some big
> >failures, where an iptables command (-Z, -A or -L) is stuck on the system
> >and then one of my cores is used at 100% and the load increases, and generally
> >I get this kernel alert :
> >http://pastebin.com/F1DL7ZZT
>
> Keep in mind that the ruleset is replaced for each HW thread and thus
> puts big requirements on memory available; as such though, I would have
> expected an OOM message rather than a Unable To Handle Kernel Paging
> Request.
I had the chance to see a 'top' running when crashing and the memory (I
got plenty =16GB) was only used about 1/4.
But the CPUs are used at full capacity ! Do you know if it is SW or HW
issue ?
It could be a coincidence but my clock is running crazy. I have got some
huge offsets recently and I am trying to solve this other issue right
now. (AFAIK there is no reason it could be link to the iptables kernel
paging request)
--
Leo Cavaille
next prev parent reply other threads:[~2011-12-05 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 13:34 [iptables] Implement huge amount of iptables make system crash Léo Cavaillé
2011-12-04 21:09 ` Jan Engelhardt
2011-12-05 0:07 ` Leo Cavaille [this message]
2011-12-05 1:11 ` Jan Engelhardt
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=20111205000758.GA25556@via.ecp.fr \
--to=chiron@via.ecp.fr \
--cc=jengelh@medozas.de \
--cc=netfilter@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