task_work: cleanup notification modes
A previous commit changed the notification mode from true/false to an int, allowing notify-no, notify-yes, or signal-notify. This was backwards compatible in the sense that any existing true/false user would translate to either 0 (on notification sent) or 1, the latter which mapped to TWA_RESUME. TWA_SIGNAL was assigned a value of 2. Clean this up properly, and define a proper enum for the notification mode. Now we have: - TWA_NONE. This is 0, same as before the original change, meaning no notification requested. - TWA_RESUME. This is 1, same as before the original change, meaning that we use TIF_NOTIFY_RESUME. - TWA_SIGNAL. This uses TIF_SIGPENDING/JOBCTL_TASK_WORK for the notification. Clean up all the callers, switching their 0/1/false/true to using the appropriate TWA_* mode for notifications. Fixes: e91b4816 ("task_work: teach task_work_add() to do signal_wake_up()") Reviewed-by:Thomas Gleixner <tglx@linutronix.de> Signed-off-by:
Jens Axboe <axboe@kernel.dk>
parent
3c532798
No related branches found
No related tags found
Showing
- arch/x86/kernel/cpu/mce/core.c 1 addition, 1 deletionarch/x86/kernel/cpu/mce/core.c
- arch/x86/kernel/cpu/resctrl/rdtgroup.c 1 addition, 1 deletionarch/x86/kernel/cpu/resctrl/rdtgroup.c
- drivers/acpi/apei/ghes.c 1 addition, 1 deletiondrivers/acpi/apei/ghes.c
- drivers/android/binder.c 1 addition, 1 deletiondrivers/android/binder.c
- fs/file_table.c 1 addition, 1 deletionfs/file_table.c
- fs/io_uring.c 7 additions, 6 deletionsfs/io_uring.c
- fs/namespace.c 1 addition, 1 deletionfs/namespace.c
- include/linux/task_work.h 8 additions, 3 deletionsinclude/linux/task_work.h
- kernel/events/uprobes.c 1 addition, 1 deletionkernel/events/uprobes.c
- kernel/irq/manage.c 1 addition, 1 deletionkernel/irq/manage.c
- kernel/sched/fair.c 1 addition, 1 deletionkernel/sched/fair.c
- kernel/task_work.c 20 additions, 10 deletionskernel/task_work.c
- security/keys/keyctl.c 1 addition, 1 deletionsecurity/keys/keyctl.c
- security/yama/yama_lsm.c 1 addition, 1 deletionsecurity/yama/yama_lsm.c
Loading
Please register or sign in to comment