时间戳

首页 > 解决方案 > sys_rt_sigreturn 中的信号掩码是如何设置的？

c - sys_rt_sigreturn 中的信号掩码是如何设置的？

问题描述

我有一个以下 C 程序，比如signal.c：

#define _GNU_SOURCE

#include <signal.h>
#include <stdlib.h>
#include <unistd.h>
#include <pthread.h>

static void *func(void *arg) {
    sleep(3);
}

int main(void) {
    pthread_t td;

    pthread_create(&td, 0, func, NULL);
    pthread_cancel(td);
    pthread_join(td, NULL);

    return 0;
}

该程序使用 musl-gcc 编译，这意味着它使用 musl-libc。

我想知道这个程序使用的系统调用实际上是如何工作的，所以我用 来检查程序strace，主要结果是：

[pid 14736] execve("./signal", ["./signal"], 0x55b68a817448 /* 72 vars */) = 0
[pid 14736] arch_prctl(ARCH_SET_FS, 0x603118) = 0
[pid 14736] set_tid_address(0x603330)   = 14736
[pid 14736] rt_sigprocmask(SIG_UNBLOCK, [RT_1 RT_2], NULL, 8) = 0
[pid 14736] mmap(NULL, 143360, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa528201000
[pid 14736] mprotect(0x7fa528203000, 135168, PROT_READ|PROT_WRITE) = 0
[pid 14736] rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [], 8) = 0
[pid 14736] clone(child_stack=0x7fa528223ed8, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|0x400000, parent_tidptr=0x7fa528223f58, tls=0x7fa528223f20, child_tidptr=0x603330) = 14737
[pid 14736] rt_sigprocmask(SIG_SETMASK, [], strace: Process 14737 attached
NULL, 8) = 0
[pid 14737] rt_sigprocmask(SIG_SETMASK, [],  <unfinished ...>
[pid 14736] rt_sigaction(SIGRT_1, {sa_handler=0x40055e, sa_mask=~[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x401820},  <unfinished ...>
[pid 14737] <... rt_sigprocmask resumed> NULL, 8) = 0
[pid 14736] <... rt_sigaction resumed> NULL, 8) = 0
[pid 14737] nanosleep({tv_sec=3, tv_nsec=0},  <unfinished ...>
[pid 14736] tkill(14737, SIGRT_1 <unfinished ...>
[pid 14737] <... nanosleep resumed> {tv_sec=2, tv_nsec=999998914}) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
[pid 14736] <... tkill resumed> )       = 0
[pid 14737] --- SIGRT_1 {si_signo=SIGRT_1, si_code=SI_TKILL, si_pid=14736, si_uid=1000} ---
[pid 14736] futex(0x7fa528223f60, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 14737] tkill(14737, SIGRT_1)       = 0
[pid 14737] rt_sigreturn({mask=[RT_1]}) = -1 EINTR (Interrupted system call)
[pid 14737] rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [RT_1], 8) = 0
[pid 14737] futex(0x7fa528223f60, FUTEX_WAKE_PRIVATE, 1) = 1
[pid 14736] <... futex resumed> )       = 0
[pid 14737] exit(0 <unfinished ...>
[pid 14736] futex(0x603330, FUTEX_WAIT, 14737, NULL <unfinished ...>
[pid 14737] <... exit resumed>)         = ?
[pid 14736] <... futex resumed> )       = 0
[pid 14737] +++ exited with 0 +++
[pid 14736] munmap(0x7fa528201000, 143360) = 0
[pid 14736] exit_group(0)               = ?
[pid 14736] +++ exited with 0 +++

让我感到困惑的是，由 设置的面具sigreturn，你可以看到它[RT_1]。据我了解，sigreturn会在被信号中断之前恢复线程的掩码。但是我们可以发现，mask set bysigprocmask只是一个空集。关注以下结果：

[pid 14737] rt_sigprocmask(SIG_SETMASK, [],  <unfinished ...>
[pid 14736] rt_sigaction(SIGRT_1, {sa_handler=0x40055e, sa_mask=~[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x401820},  <unfinished ...>
[pid 14737] <... rt_sigprocmask resumed> NULL, 8) = 0
[pid 14736] <... rt_sigaction resumed> NULL, 8) = 0
[pid 14737] nanosleep({tv_sec=3, tv_nsec=0},  <unfinished ...>
[pid 14736] tkill(14737, SIGRT_1 <unfinished ...>
[pid 14737] <... nanosleep resumed> {tv_sec=2, tv_nsec=999998914}) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
[pid 14736] <... tkill resumed> )       = 0
[pid 14737] --- SIGRT_1 {si_signo=SIGRT_1, si_code=SI_TKILL, si_pid=14736, si_uid=1000} ---
[pid 14736] futex(0x7fa528223f60, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 14737] tkill(14737, SIGRT_1)       = 0
[pid 14737] rt_sigreturn({mask=[RT_1]}) = -1 EINTR (Interrupted system call)
[pid 14737] rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [RT_1], 8) = 0

换句话说，我不能理解的一件事是，掩码[RT_1]最后是怎么来的（根据 的第三个参数给出的结果rt_sigprocmask，它代表旧的信号掩码）？由于一开始它被设置为空，我找不到任何其他系统调用更改掩码。

我猜可能是内核在某个时候改变了这个掩码，也许它会在某些情况下这样做，例如，内核添加sigaction了线程进入信号处理程序时指定的掩码，并将它们恢复到sigreturn. 但是相关的参考资料太难找了。

有人可以就此提供任何建议吗？提前致谢。

标签： clinux-kernelpthreadssignals

解决方案

您所看到的是 pthread 库的内部工作原理。换句话说，负责在信号掩码中添加/删除这些信号的不是内核，而是 pthread 库。pthread 库在内部使用实时信号来管理线程。strace将它们显示为RT_n. 它们被添加到掩码中/从掩码中移除的事实不应该让您担心。

man 7 signal在“实时信号”部分中查找有关实时信号的更多信息。

推荐阅读