Note: if anyone else is wondering what may be deadlocking 2.2.17+
in the context of http connects over ethernet (assuming that it is not the
ethernet driver itself): it is also not the httpd server's use of linux
kernel threads (wn is single threaded). And there isn't much going
on in the background when this is tested. A bunch of daemons are
running, but only the k*d (kupdated, kflushd, kpiod, kswapd, klogd)
and utmpd besides the httpd server itself ever run during the test.
Tests were conducted both with inetd handling the http connect and with
wnsd listening on the http port directly, no difference.
Unless one of those k*d daemons uses kernel threads, kernel threads
exported to user space are not possibly the source of the deadlock.
(Might have looked that way due to the stack corruption in the httpd
parent that strace seems to see a few connects before the kernel
deadlock.)
Regards,
Clayton Weaver
<mailto:[email protected]>
(Seattle)
"Everybody's ignorant, just in different subjects." Will Rogers