[lkml]   [2015]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/4] Fix kmemleak races on the disable/error path
This is a follow-up to the initial patch fixing the kmemleak_scan page
fault during kmemleak disabling:

The first patch is pretty much the same, apart from a clearer
(hopefully) commit log and code comment regarding the ordering of
kmemleak_free_enabled with the scanning thread. The race between
kmemleak_free() and kmemleak_do_cleanup() is fixed in the second patch.

The third patch fixes a potential deadlock on scan_mutex between the
kmemleak_scan_thread and kmemleak_do_cleanup().

The fourth patch is more of a theoretical scenario but worth fixing the
lock acquiring order.

Catalin Marinas (4):
mm: kmemleak: Allow safe memory scanning during kmemleak disabling
mm: kmemleak: Fix delete_object_*() race when called on the same
memory block
mm: kmemleak: Do not acquire scan_mutex in kmemleak_do_cleanup()
mm: kmemleak: Avoid deadlock on the kmemleak object insertion error

mm/kmemleak.c | 75 +++++++++++++++++++++++++++++++++++++++++------------------
1 file changed, 53 insertions(+), 22 deletions(-)

 \ /
  Last update: 2015-06-08 17:21    [W:0.026 / U:0.556 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site