Let proc_raise() call into pksignal() directly.

[ed]

Summary

As discussed with kib@ in response to r285404, don't call into
kern_sigaction() within proc_raise() to reset the signal to the default
action before delivery. We'd better do that during image execution.

Change the code to simply use pksignal(), so we don't waste cycles on
functions like pfind() to look up the currently running process itself.

Test Plan

This change has also been pushed into the cloudabi branch on GitHub. The
raise() tests still seem to pass.

[kib]

s/process creation/image execution/ in the explanation.

sys/compat/cloudabi/cloudabi_proc.c

99 ↗

(On Diff #6915)

Should this condition be sig >= nitems() or sig > nitems ? Zero-indexed element is not a real signal.

[ed]

In D3076#60795, @kib wrote:

s/process creation/image execution/ in the explanation.

Done!

sys/compat/cloudabi/cloudabi_proc.c

99 ↗

(On Diff #6915)

We could remove the zero'th element from this array, but it would have the disadvantage that we'd have to write [CLOUDABI_SIG... - 1] = SIG... for every array member and index it using signals[uap->sig - 1]. I decided to be a bit more lazy here and just leave the element in there. This way the intent becomes a bit more obvious.

Alternatively we could remove the [] = designators entirely and list all the signals in the right order, but this way it becomes more clear that we don't map one of the signals incorrectly.

[kib]

sys/compat/cloudabi/cloudabi_proc.c

99 ↗

(On Diff #6915)

Ok, I am not about the removal of zero element. The '>=' condition seems to be right thing to do.