signals: introduce send_sigkill() helper
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | signals: introduce send_sigkill() helperinclude/ kernel/ | +10 | 4 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | KAMEZAWA Hiroyuki | KOSAKI Motohiro |
|---|---|---|
| 1/1 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/1] signals: introduce send_sigkill() helper
Quoted 15 lines · Oleg Nesterov
Review static int __oom_kill_process(struct task_struct *p, struct mem_cgroup *mem) · line 402
Quoted 7 lines
(quoted diff) +1
-1@@ -399,7 +399,7 @@ static int __oom_kill_process(struct task_struct *p, struct mem_cgroup *mem) p->rt.time_slice = HZ; set_tsk_thread_flag(p, TIF_MEMDIE); - force_sig(SIGKILL, p); + send_sig(SIGKILL, p, 1);This is not right, we need
send_sig(SIGKILL, p, 0). Better yet,send_sig_info(SIGKILL, SEND_SIG_NOINFO). I thinksend_sig()should die.The reason is that
si_fromuser()must be true, otherwise we can't kill theSIGNAL_UNKILLABLE(sub-namespace inits) tasks.
Quoted 7 lines
Oh. This reminds me, we really need the trivial (but annoying) cleanups here. The usage of
SEND_SIG_constants is messy, and they should be renamed at least.And in fact, we need the new one which acts like
SEND_SIG_FORCEDbutsi_fromuser(). We do not want to allocate the memory when the caller isoom_killorzap_pid_ns_processes().
I tried to make some simple cleanups right now, but this really needs time and discussion.
So. If we are going to remove force_sig() in mm/oom_kill.c (and I think we should), I'd like to add the trivial helper first.
Oleg.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>