Skip to content

Commit 98008ff

Browse files
committedJul 9, 2019
vmmon: fix HostIF_SetFastClockRate() not to use force_sig()
Commit 3cf5d076fb4d ("signal: Remove task parameter from force_sig") in v5.3-rc1 drops second argument of force_sig(); before that, all callers which passed something else than current task as second argument were fixed, mostly to use send_sig() instead. The situation in HostIF_SetFastClockRate() is the same as e.g. in bpfilter call fixed by commit 1dfd1711de29 ("signal/bpfilter: Fix bpfilter_kernl to use send_sig not force_sig"): locking in force_sig_info() cannot handle task exiting and using force_sig() for SIGKILL is pointless anyway as this signal cannot be blocked. As send_sig() is present with unchanged signature since the pre-git era, we can use send_sig() unconditionally, regardless of kernel version.
1 parent 06587f7 commit 98008ff

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎vmmon-only/linux/hostif.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -3403,7 +3403,7 @@ HostIF_SetFastClockRate(unsigned int rate) // IN: Frequency in Hz.
34033403
}
34043404
} else {
34053405
if (linuxState.fastClockThread) {
3406-
force_sig(SIGKILL, linuxState.fastClockThread);
3406+
send_sig(SIGKILL, linuxState.fastClockThread, 1);
34073407
kthread_stop(linuxState.fastClockThread);
34083408

34093409
linuxState.fastClockThread = NULL;

0 commit comments

Comments
 (0)
Please sign in to comment.