Understanding the Linux Kernel by Bovet Daniel P

Author:Bovet, Daniel P. [Bovet, Daniel P.]
Language: eng
Format: azw3
Tags: COMPUTERS / Operating Systems / Linux
ISBN: 9780596158804
Publisher: O'Reilly Media
Published: 2008-12-16T16:00:00+00:00

SA_ONSTACK

Use an alternative stack for the signal handler (see the later section "Catching the Signal“)

SA_RESTART

Interrupted system calls are automatically restarted (see the later section "Reexecution of System Calls“)

SA_NODEFER, SA_NOMASK

Do not mask the signal while executing the signal handler

SA_RESETHAND,

SA_ONESHOT

Reset to default action after executing the signal handler

The pending signal queues

As we have seen in Table 11-2 earlier in the chapter, there are several system calls that can generate a signal: some of them — kill( ) and rt_sigqueueinfo( ) — send a signal to a whole thread group, while others — tkill( ) and tgkill( ) — send a signal to a specific process.

Thus, in order to keep track of what signals are currently pending, the kernel associates two pending signal queues to each process:

The shared pending signal queue, rooted at the shared_pending field of the signal descriptor, stores the pending signals of the whole thread group.

The private pending signal queue, rooted at the pending field of the process descriptor, stores the pending signals of the specific (lightweight) process.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.