Re: [ANNOUNCE] ipset 6.5 released

[Mr Dash Four <mr.dash.four@googlemail.com>]

> The uninitialized bytes are OK and there is no memory leak or corruption.
>   
I am able to now reproduce the error, having applied your patch Jozsef, 
rebuilt the kernel, updated the whole image on that machine and 
rebooted. This is what happens:

All sets are now loaded, *except* the last file where I get the 
segmentation fault error I described earlier, i.e, something like this:

May 22 01:25:20 dmz1 kernel: [ 1361.321376] ipset[2819]: segfault at 0 
ip 00e26655 sp bfdad710 error 4 in libmnl.so.0.0.1[e24000+4000]
May 22 01:26:39 dmz1 kernel: [ 1440.120529] ipset[2841]: segfault at 0 
ip 002d7655 sp bfbe7b10 error 4 in libmnl.so.0.0.1[2d5000+4000]

I started to narrow this down and the first culprit seems to be the 
following 2 statements:

n priviledged-ports bitmap:port range 1-1023 timeout 0
a priviledged-ports 1-1023

When I removed the above 2 statements I am then getting this:

ipset v6.5: Error in line 4: Internal protocol error

No segmentation fault! I narrowed the latest error down to the following 
2 statements:

n test-net bitmap:ip range 10.1.1.172/29 timeout 0
a test-net 10.1.1.172/29

I then removed those as well. Tried again - segmentation fault error. I 
then removed the following 3 statements, which were next in line:

n test-ports bitmap:port range 12770-19999 timeout 0
a test-ports 12770-12784
a test-ports 19999

Next, another segmentation fault error, it turns out the culprit this 
time was 2 statements which were further down the line from this file:

n test-port bitmap:port range 29950-29950 timeout 0
a test-port 29950

Removed these and guess what - segmentation fault error again, at which 
point I bloody gave up! ipset 4.5 it is!