diff options
| author | Christian Brauner <brauner@kernel.org> | 2026-08-24 14:08:16 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-08-31 10:05:12 +0200 |
| commit | 22b7f491be8f93ff72de0a3fe02b8ee9e64d3f21 (patch) | |
| tree | 1ad3a99f2d73ec389985f2a1e4e0df043bda9776 /tools/lib/python/kdoc/python_version.py | |
| parent | cee9395acd8043be0644b25c34bfa86623f2b935 (diff) | |
| download | linux-next-22b7f491be8f93ff72de0a3fe02b8ee9e64d3f21.tar.gz linux-next-22b7f491be8f93ff72de0a3fe02b8ee9e64d3f21.zip | |
signal: allow taks to temporarily block TIF_NOTIFY_SIGNAL
TIF_NOTIFY_SIGNAL is used to kick a task in uninterruptible sleep to
return to userspace and run task work and then go back to sleep. This
mechanism works well but breaks e.g., coredumps. dump_interrupted() only
allows fatal signals to interrupt a coredump and the whole regular write
path going to actual filesystems is impervious to TIF_NOTIFY_SIGNAL as
well.
Add PF_NO_NOTIFY_SIGNAL and helpers to raise and restore it. This is the
same approach as memalloc_nofs_save(). signal_pending() will not report
a fake pending signal via TIF_NOTIFY_SIGNAL if inside a
PF_NO_NOTIFY_SIGNAL section.
No functional changes.
Link: https://patch.msgid.link/20260824-work-tif_notify_signal-v2-1-6609e42b3157@kernel.org
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions