| commit | eae81d70574e923ce3c59078b8df857ae192efa6 | |
| author | Florian Weimer <fweimer@redhat.com> | |
| Fri, 1 Oct 2021 16:16:41 +0000 (1 18:16 +0200) | ||
| committer | Florian Weimer <fweimer@redhat.com> | |
| Fri, 1 Oct 2021 16:16:41 +0000 (1 18:16 +0200) | ||
| tree | 7e7ed9a2ae46d5f6e8129871949d23a750fdced2 | treesnapshot (tar.gz zip) |
| parent | 176c88f5214d8107d330971cbbfbbba5186a111f | commitdiff |
nptl: pthread_kill must send signals to a specific thread [BZ #28407]
The choice between the kill vs tgkill system calls is not just about
the TID reuse race, but also about whether the signal is sent to the
whole process (and any thread in it) or to a specific thread.
This was caught by the openposix test suite:
LTP: openposix test suite - FAIL: SIGUSR1 is member of new thread pendingset.
<https://gitlab.com/cki-project/kernel-tests/-/issues/764>
Fixes commit 526c3cf11ee9367344b6b15d669e4c3cb461a2be ("nptl: Fix race
between pthread_kill and thread exit (bug 12889)").
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>
The choice between the kill vs tgkill system calls is not just about
the TID reuse race, but also about whether the signal is sent to the
whole process (and any thread in it) or to a specific thread.
This was caught by the openposix test suite:
LTP: openposix test suite - FAIL: SIGUSR1 is member of new thread pendingset.
<https://gitlab.com/cki-project/kernel-tests/-/issues/764>
Fixes commit 526c3cf11ee9367344b6b15d669e4c3cb461a2be ("nptl: Fix race
between pthread_kill and thread exit (bug 12889)").
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>
| nptl/pthread_kill.c | diffblobblamehistory | |
| sysdeps/pthread/Makefile | diffblobblamehistory | |
| sysdeps/pthread/tst-pthread-raise-blocked-self.c | [new file with mode: 0644] | blob |