19:39 < caker> jdike:
http://www.theshore.net/~caker/uml/cras ... le-output/19:41 < caker> jdike: very easy to reproduce -- just a script, another file with IPs, and ping flood the UML's IP
19:51 < caker> time for food .. brb
20:14 < jdike> Blocking 222.64.190.133...
20:14 < jdike> Jan 11 20:06:28 usermode syslogd: recvfrom unix: Resource temporarily unavailable
20:14 < jdike> Segmentation fault
20:14 < jdike> Looking like a stack overflow
20:16 < jdike> and that doesn't surprise me too much
20:27 < jdike> When caker comes back, someone tell him that his problem smells heavily of a stack overflow
20:28 < jdike> Probably easily fixed, although I need to think about it some
20:35 < caker> jdike: thanks for taking a look at that
20:37 < jdike> caker: For some reason, you can't make the idle thread stack overflow, or at least not badly enough to cause a crash
20:37 < jdike> caker: however when its doing something else in the kernel, and I'm guessing iptables is generating deep stacks on its own, it does cause a crash
20:38 < jdike> caker: theory only, I haven't poked at it at all yet
20:38 < caker> jdike: ok -- glad it was easy enough for you to reproduce
20:38 < jdike> caker: yup
20:38 < jdike> caker: the right test case is a wondrous thing
20:40 * jdike disappears again