bugzilla-daemon@bugzilla.netfilter.org
2006-Jun-06 02:00 UTC
[Bug 485] Stresstesting ipset crashes kernel
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=485 ------- Additional Comments From bugzilla.netfilter@neufeind.net 2006-06-06 02:00 MET ------- I tried to track down the problem meanwhile. It turns out that e.g. in a row of roughly 480 "ipset -A" (nethash) in a row the system once hangs at around 300 executed statements while it hangs around 370 the next time. So this does not seem to be reproducable. But I did the same tries on an otherwise identical i386-system with the same centos-libraries etc - just recompiled the ipset-libs I added/backported. On i386 it works fine (even 30 times all 480 adds in a row), while it crashes on x86_64. Could there be a bug related to the architecture (64-bit)? -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon@bugzilla.netfilter.org
2006-Jun-06 02:03 UTC
[Bug 485] Stresstesting ipset crashes kernel
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=485 ------- Additional Comments From bugzilla.netfilter@neufeind.net 2006-06-06 02:03 MET ------- Oh, just for the record: The "workaround"-part of my first description did not proof as reliable - even in those cases later the system crashed during repeated runs. -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon@bugzilla.netfilter.org
2006-Jun-06 10:52 UTC
[Bug 485] Stresstesting ipset crashes kernel
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=485 kadlec@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From kadlec@netfilter.org 2006-06-06 10:52 MET ------- I suspect too that it's an architecture-dependent bug - I have never tried ipset on 64-bit systems. Is there any kernel message related to the crash/hang? -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
bugzilla-daemon@bugzilla.netfilter.org
2006-Jun-06 11:12 UTC
[Bug 485] Stresstesting ipset crashes kernel
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=485 bugzilla.netfilter@neufeind.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From bugzilla.netfilter@neufeind.net 2006-06-06 11:12 MET ------- Unfortunately I can't "see" an error. Any oops that might occur on the console currently I can't read since it's a remote machine :-) During the last hours I reinstalled most parts of the libraries, compiled my "backported" ipset again, did some stresstesting. To my surprise so far the system did not yet crash again. Interesting. For now I'll make this bug a "works-for-me" and will reopen it if needed. Thank you very much for the quick feedback. -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Possibly Parallel Threads
- [Bug 485] New: Stresstesting ipset crashes kernel
- [Bug 640] New: ipset-4.2 : ipset -T <some_setlist> <address> always negative
- [Bug 719] New: ipset restore fails randomly
- [Bug 1750] New: 'ipset save' does not save in format loadable by systemd (it saves in 'ipset list' format)
- [Bug 880] New: ipset doesn't refresh the timeout for an existing entry when the table is FULL.