diff options
author | Anton Vorontsov <anton.vorontsov@linaro.org> | 2012-02-06 20:29:41 +0400 |
---|---|---|
committer | Simon Shields <keepcalm444@gmail.com> | 2016-06-13 14:47:33 +1000 |
commit | e6edd4723129b31402ad2da3d579abfaf5286f4d (patch) | |
tree | a7f15ccef50836560f987a077386cbe90af6abf0 /drivers/char/diag | |
parent | fa24b26d017dc88a9b1956dab2ed898e4d4f17ad (diff) | |
download | kernel_samsung_smdk4412-e6edd4723129b31402ad2da3d579abfaf5286f4d.tar.gz kernel_samsung_smdk4412-e6edd4723129b31402ad2da3d579abfaf5286f4d.tar.bz2 kernel_samsung_smdk4412-e6edd4723129b31402ad2da3d579abfaf5286f4d.zip |
staging: android/lowmemorykiller: Don't grab tasklist_lock
Grabbing tasklist_lock has its disadvantages, i.e. it blocks
process creation and destruction. If there are lots of processes,
blocking doesn't sound as a great idea.
For LMK, it is sufficient to surround tasks list traverse with
rcu_read_{,un}lock().
>From now on using force_sig() is not safe, as it can race with an
already exiting task, so we use send_sig() now. As a downside, it
won't kill PID namespace init processes, but that's not what we
want anyway.
Suggested-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Conflicts:
drivers/staging/android/lowmemorykiller.c
Diffstat (limited to 'drivers/char/diag')
0 files changed, 0 insertions, 0 deletions