Re: 9.1: forcible coredump -> panic

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> kcopy() at ...
>> uiomove() at ...
[...]
>> coredump() at ...
>> deadman_timeout() at ...
>> callout_softclock() at ...
>> softint_dispatch() at ...

> Youâ??re not supposed to access user-space from a soft-int handler.  You nee$

That certainly would qualify as the stupid thing I was doing which I
figured must exist!

As for "dispatch[ing] to another kernel thread"...can a soft-int create
a kernel thread, or do I need to precreate the thread and have it in my
back pocket so I just need to wake it up when the callout fires?

Might this be a good use case for workqueue(9)?  The manpage makes it
look as though that would manage the thread(s) and queue(s) and such
for me, which feels like a significant benefit in this case.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B