diff options
author | kib <kib@FreeBSD.org> | 2009-11-17 11:39:15 +0000 |
---|---|---|
committer | kib <kib@FreeBSD.org> | 2009-11-17 11:39:15 +0000 |
commit | 2d08f816e13d4eca3a96eb24f578541791a335e7 (patch) | |
tree | c59c7fddba5c77496f61d018fe1c5c004cf33224 /contrib/sendmail/rmail | |
parent | 45887d4e283c9ac9f5830e01dd3a82881571fded (diff) | |
download | FreeBSD-src-2d08f816e13d4eca3a96eb24f578541791a335e7.zip FreeBSD-src-2d08f816e13d4eca3a96eb24f578541791a335e7.tar.gz |
Among signal generation syscalls, only sigqueue(2) is allowed by POSIX
to fail due to lack of resources to queue siginfo. Add KSI_SIGQ flag
that allows sigqueue_add() to fail while trying to allocate memory for
new siginfo. When the flag is not set, behaviour is the same as for
KSI_TRAP: if memory cannot be allocated, set bit in sq_kill. KSI_TRAP is
kept to preserve KBI.
Add SI_KERNEL si_code, to be used in siginfo.si_code when signal is
generated by kernel. Deliver siginfo when signal is generated by kill(2)
family of syscalls (SI_USER with properly filled si_uid and si_pid), or
by kernel (SI_KERNEL, mostly job control or SIGIO). Since KSI_SIGQ flag
is not set for the ksi, low memory condition cause old behaviour.
Keep psignal(9) KBI intact, but modify it to generate SI_KERNEL
si_code. Pgsignal(9) and gsignal(9) now take ksi explicitely. Add
pksignal(9) that behaves like psignal but takes ksi, and ddb kill
command implemented as pksignal(..., ksi = NULL) to not do allocation
while in debugger.
While there, remove some register specifiers and use ANSI C prototypes.
Reviewed by: davidxu
MFC after: 1 month
Diffstat (limited to 'contrib/sendmail/rmail')
0 files changed, 0 insertions, 0 deletions