https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=68
matthias.kehlenbeck@stud.uni-hannover.de changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|RedHat Linux |Gentoo
------- Additional Comments From matthias.kehlenbeck@stud.uni-hannover.de
2003-05-14 14:57 -------
I just installed a Gentoo Linux box and have exactly the same problem. I use an
AMD K6-2 300 with 164mb RAM and latest BIOS update. I am able to reproduce the
error. It happens EVERY time I try to make a connection from a workstation to
this Linux box via http.
If you would like me to provide any further information please do not hesitate
to ask.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=68 ------- Additional Comments From hno@marasystems.com 2003-05-26 19:33 ------- I have a similar problem in the ip_pool module. Is extending this module a bit and needs to allocate memory. If kmalloc() needs to extend the slab while running the nf getsockopt then slab.c BUG():s wanting GPF_ATOMIC because it thinks the code is called from interrupt context (in_interrupt() true).. There is a few locks held at this time, but nothing critical as far as I know unless the netfilter core does something strange on nf getsockopt calls. The code I am working on is called as a nf_getsockopt custom handler. Note the slab.c BUG() wil not always trigger. It only BUG()s if the slab cache needs to be grown. This is on a 2.4.20 kernel. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=68 ------- Additional Comments From hno@marasystems.com 2003-05-26 19:55 ------- Found my ip_pool extension problem and it is not related to netfilter. As soon as a write_lock_bh() is held you are considered to be in interrupt context by the slab allocator. Sorry for cluttering down this bug report with unrelated issues but it did look related at first.. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.