From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.5 released
Date: Sat, 21 May 2011 20:42:05 +0100 [thread overview]
Message-ID: <4DD8158D.4040306@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105170941590.31848@blackhole.kfki.hu>
> Yes, it was fixed, the last one ("Fix adding ranges to hash types") covers
> that.
>
I disagree! I am still experiencing the same problems I've had with
ipset 6.4, despite those being "fixed". When I try to load a set
containing about 15k elements I get variations on the same type of error
below:
ipset v6.5: Error in line 3556: Element cannot be added to the set: it's
already added
ipset v6.5: Error in line 3653: Element cannot be added to the set: it's
already added
ipset v6.5: Error in line 3340: Element cannot be added to the set: it's
already added
ipset v6.5: Error in line 3266: Element cannot be added to the set: it's
already added
ipset v6.5: Error in line 3653: Element cannot be added to the set: it's
already added
ipset v6.5: Error in line 11187: Hash is full, cannot add more elements
ipset v6.5: Error in line 11182: Hash is full, cannot add more elements
ipset v6.5: Error in line 11185: Hash is full, cannot add more elements
ipset v6.5: Error in line 11186: Hash is full, cannot add more elements
The above happens when I try to use restore with the same file (i.e. the
file contents does *not* change). On top of it all I also started
getting this:
May 21 19:47:49 dmz1 kernel: [ 2103.322341] ipset[2827]: segfault at 0
ip 004f6655 sp bf9125f0 error 4 in libmnl.so.0.0.1[4f4000+4000]
May 21 19:39:03 dmz1 kernel: [ 1576.402070] ipset[2777]: segfault at 0
ip 006ea655 sp bfcfd900 error 4 in libmnl.so.0.0.1[6e8000+4000]
May 21 19:47:49 dmz1 kernel: [ 2103.322341] ipset[2827]: segfault at 0
ip 004f6655 sp bf9125f0 error 4 in libmnl.so.0.0.1[4f4000+4000]
May 21 19:57:32 dmz1 kernel: [ 2685.725299] ipset[2870]: segfault at 0
ip 00339655 sp bf8bac90 error 4 in libmnl.so.0.0.1[337000+4000]
May 21 20:01:48 dmz1 kernel: [ 2942.232408] ipset[2913]: segfault at 0
ip 00baa655 sp bfa25d80 error 4 in libmnl.so.0.0.1[ba8000+4000]
May 21 20:09:18 dmz1 kernel: [ 3392.073377] ipset[2928]: segfault at 0
ip 00470655 sp bfcb43c0 error 4 in libmnl.so.0.0.1[46e000+4000]
May 21 20:10:57 dmz1 kernel: [ 3490.388755] ipset[2941]: segfault at 0
ip 00b8a655 sp bffb92c0 error 4 in libmnl.so.0.0.1[b88000+4000]
May 21 20:12:36 dmz1 kernel: [ 3589.622479] ipset[2954]: segfault at 0
ip 009bf655 sp bf8fef80 error 4 in libmnl.so.0.0.1[9bd000+4000]
May 21 20:13:21 dmz1 kernel: [ 3634.433419] ipset[2966]: segfault at 0
ip 00d11655 sp bf9ae7a0 error 4 in libmnl.so.0.0.1[d0f000+4000]
May 21 20:13:28 dmz1 kernel: [ 3641.484628] ipset[2977]: segfault at 0
ip 005e7655 sp bfedb090 error 4 in libmnl.so.0.0.1[5e5000+4000]
May 21 20:13:42 dmz1 kernel: [ 3656.205294] ipset[2988]: segfault at 0
ip 009cb655 sp bfae5b80 error 4 in libmnl.so.0.0.1[9c9000+4000]
May 21 20:15:31 dmz1 kernel: [ 3765.137306] ipset[3001]: segfault at 0
ip 0019e655 sp bfe3fff0 error 4 in libmnl.so.0.0.1[19c000+4000]
libmnl is 1.0.1. I have then tried to play a bit with the hashsize
value, but gave up when I reached 16777216! ipset though was still
insisting that the hash size is "full":
maxelem 15000 hashsize 4194304
ipset v6.5: Error in line 11191: Hash is full, cannot add more elements
maxelem 15000 hashsize 8388608
ipset v6.5: Error in line 11191: Hash is full, cannot add more elements
maxelem 15000 hashsize 16777216
ipset v6.5: Error in line 11191: Hash is full, cannot add more elements
-bash-4.1# ipset -L -terse test
Name: test
Type: hash:net
Header: family inet hashsize 16777216 maxelem 15000 timeout 0
Size in memory: 134937948
References: 0
So, 134MB of RAM is not enough for a set consisting of 15k members?
Right! I am reverting to 4.5 again as this is crazy!
next prev parent reply other threads:[~2011-05-21 19:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 13:50 [ANNOUNCE] ipset 6.5 released Jozsef Kadlecsik
2011-05-16 15:41 ` Mr Dash Four
2011-05-17 7:42 ` Jozsef Kadlecsik
2011-05-17 11:03 ` Mr Dash Four
2011-05-17 11:51 ` Jozsef Kadlecsik
2011-05-17 15:23 ` Mr Dash Four
2011-05-17 18:36 ` Mr Dash Four
2011-05-18 7:54 ` Jozsef Kadlecsik
2011-05-18 10:59 ` Mr Dash Four
2011-05-18 11:22 ` Jozsef Kadlecsik
2011-05-21 19:42 ` Mr Dash Four [this message]
2011-05-21 19:45 ` Jozsef Kadlecsik
2011-05-21 19:58 ` Jozsef Kadlecsik
2011-05-21 20:11 ` Mr Dash Four
2011-05-21 21:31 ` Jozsef Kadlecsik
2011-05-21 21:33 ` Jan Engelhardt
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 21:52 ` Jan Engelhardt
2011-05-21 23:08 ` Jozsef Kadlecsik
2011-05-22 1:01 ` Mr Dash Four
2011-05-22 10:05 ` Jozsef Kadlecsik
2011-05-22 10:36 ` Jozsef Kadlecsik
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 21:21 ` Jozsef Kadlecsik
2011-05-22 21:32 ` Mr Dash Four
2011-05-22 15:00 ` Jan Engelhardt
2011-05-22 13:57 ` Mr Dash Four
2011-05-22 14:05 ` Mr Dash Four
2011-05-21 21:51 ` Mr Dash Four
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 22:28 ` Jozsef Kadlecsik
2011-05-21 22:41 ` Jozsef Kadlecsik
2011-05-21 22:44 ` Mr Dash Four
2011-05-21 22:42 ` Mr Dash Four
2011-05-22 14:52 ` Mr Dash Four
2011-05-21 22:15 ` Mr Dash Four
2011-05-21 22:31 ` Jozsef Kadlecsik
2011-05-21 22:42 ` Mr Dash Four
2011-05-21 22:49 ` Jozsef Kadlecsik
2011-05-21 22:57 ` Mr Dash Four
2011-05-21 23:25 ` Jozsef Kadlecsik
2011-05-21 23:33 ` Mr Dash Four
2011-05-22 9:56 ` Jozsef Kadlecsik
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=4DD8158D.4040306@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--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 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.