Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

kmemleak: Do not report new leaked objects if the scanning was stopped

Browse source 
If the scanning was stopped with a signal, it is possible that some
objects are left with a white colour (potential leaks) and reported. Add
a check to avoid reporting such objects.

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
This commit is contained in:
Catalin Marinas 2009-06-29 17:13:56 +01:00
parent acf4968ec9
commit 17bb9e0d90
1 changed files with 10 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
mm/kmemleak.c
View file

@ -1029,6 +1029,12 @@ static void kmemleak_scan(void)
} }
WARN_ON(!list_empty(&gray_list)); WARN_ON(!list_empty(&gray_list));
/*
* If scanning was stopped do not report any new unreferenced objects.
*/
if (scan_should_stop())
return;
/* /*
* Scanning result reporting. * Scanning result reporting.
*/ */
@ -1184,11 +1190,10 @@ static int kmemleak_seq_show(struct seq_file *seq, void *v)
unsigned long flags; unsigned long flags;
spin_lock_irqsave(&object->lock, flags); spin_lock_irqsave(&object->lock, flags);
if (!unreferenced_object(object)) if ((object->flags & OBJECT_REPORTED) && unreferenced_object(object)) {
goto out;
print_unreferenced(seq, object); print_unreferenced(seq, object);
reported_leaks++; reported_leaks++;
out: }
spin_unlock_irqrestore(&object->lock, flags); spin_unlock_irqrestore(&object->lock, flags);
return 0; return 0;
} }