summaryrefslogtreecommitdiffstats
path: root/scripts/leaking_addresses.pl
diff options
context:
space:
mode:
authorTobin C. Harding <me@tobin.cc>2018-03-01 16:49:55 -0500
committerTobin C. Harding <me@tobin.cc>2018-04-06 18:50:34 -0400
commitc73dff595f259736a90f52b38cf5798abeae4a3c (patch)
treed8c32846abfa3a47ceeb6c80aa368dfc2fcbdb71 /scripts/leaking_addresses.pl
parent2306a67745ebdf3f98bc954248b74a3f1d57cdc2 (diff)
leaking_addresses: check if file name contains address
Sometimes files may be created by using output from printk. As the scan traverses the directory tree we should parse each path name and check if it is leaking an address. Add check for leaking address on each path name. Suggested-by: Tycho Andersen <tycho@tycho.ws> Acked-by: Tycho Andersen <tycho@tycho.ws> Signed-off-by: Tobin C. Harding <me@tobin.cc>
Diffstat (limited to 'scripts/leaking_addresses.pl')
-rwxr-xr-xscripts/leaking_addresses.pl12
1 files changed, 12 insertions, 0 deletions
diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
index ba5f9709bced..6a897788f5a7 100755
--- a/scripts/leaking_addresses.pl
+++ b/scripts/leaking_addresses.pl
@@ -463,6 +463,16 @@ sub parse_file
463 close $fh; 463 close $fh;
464} 464}
465 465
466# Checks if the actual path name is leaking a kernel address.
467sub check_path_for_leaks
468{
469 my ($path) = @_;
470
471 if (may_leak_address($path)) {
472 printf("Path name may contain address: $path\n");
473 }
474}
475
466# Recursively walk directory tree. 476# Recursively walk directory tree.
467sub walk 477sub walk
468{ 478{
@@ -485,6 +495,8 @@ sub walk
485 495
486 next if (skip($path)); 496 next if (skip($path));
487 497
498 check_path_for_leaks($path);
499
488 if (-d $path) { 500 if (-d $path) {
489 push @dirs, $path; 501 push @dirs, $path;
490 next; 502 next;