runsv: robustify signal handling - SIGTERM to child between vfork and exec could mess things up
While at it, rename bb_signals_recursive_norestart() to bb_signals_norestart(): "recursive" was implying we are setting SA_NODEFER allowing signal handler to be entered recursively, but we do not do that. function old new delta bb_signals_norestart - 70 +70 startservice 380 394 +14 bb_signals_recursive_norestart 70 - -70 ------------------------------------------------------------------------------ (add/remove: 1/1 grow/shrink: 1/0 up/down: 84/-70) Total: 14 bytes Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
		| @@ -106,7 +106,7 @@ int showkey_main(int argc UNUSED_PARAM, char **argv) | ||||
| 		xioctl(STDIN_FILENO, KDSKBMODE, (void *)(ptrdiff_t)((option_mask32 & OPT_k) ? K_MEDIUMRAW : K_RAW)); | ||||
|  | ||||
| 		// we should exit on any signal; signals should interrupt read | ||||
| 		bb_signals_recursive_norestart(BB_FATAL_SIGS, record_signo); | ||||
| 		bb_signals_norestart(BB_FATAL_SIGS, record_signo); | ||||
|  | ||||
| 		// inform user that program ends after time of inactivity | ||||
| 		printf(press_keys, "10s after last keypress"); | ||||
|   | ||||
		Reference in New Issue
	
	Block a user