From: kaiwan.billimoria@gmail.com
To: "Tobin C. Harding" <me@tobin.cc>
Cc: linux-kernel@vger.kernel.org,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: [PATCH 2/2] scripts: leaking_addresses: help screen updates
Date: Thu, 23 Nov 2017 10:45:31 +0530 [thread overview]
Message-ID: <1511414131.12425.14.camel@gmail.com> (raw)
The current leaking_addresses.pl script only supports showing "leaked"
64-bit kernel virtual addresses. This patch modifies the "help" screen in the
following manner:
- the '--raw', '--suppress-dmesg', '--squash-by-path' and '--squash-by-filename'
option switches are only meaningful when the '--input-raw=' option switch is
used. So, indent the 'Help' screen lines to reflect the fact.
- an additional example demonstrating usage of the new '--page-offset'
parameter.
Feedback welcome..
Signed-off-by: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
---
diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
index 7ca218221486..3832abb743d7 100755
--- a/scripts/leaking_addresses.pl
+++ b/scripts/leaking_addresses.pl
@@ -105,10 +105,10 @@ Options:
-o, --output-raw=<file> Save results for future processing.
-i, --input-raw=<file> Read results from file instead of scanning.
- --raw Show raw results (default).
- --suppress-dmesg Do not show dmesg results.
- --squash-by-path Show one result per unique path.
- --squash-by-filename Show one result per unique filename.
+ --raw Show raw results (default).
+ --suppress-dmesg Do not show dmesg results.
+ --squash-by-path Show one result per unique path.
+ --squash-by-filename Show one result per unique filename.
--page-offset=<hex> PAGE_OFFSET value (for 32-bit kernels).
-d, --debug Display debugging output.
-h, --help, --version Display this help and exit.
@@ -124,6 +124,10 @@ Examples:
# View summary report.
$0 --input-raw scan.out --squash-by-filename
+ # (On a 32-bit system with a 2GB:2GB VMSPLIT), pass PAGE_OFFSET value
+ # as a parameter
+ $0 --page-offset=0x80000000
+
Scans the running (32 or 64 bit) kernel for potential leaking addresses.
EOM
next reply other threads:[~2017-11-23 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 5:15 kaiwan.billimoria [this message]
2017-11-24 5:59 ` [PATCH 2/2] scripts: leaking_addresses: help screen updates Tobin C. Harding
2017-11-24 7:21 ` Kaiwan N Billimoria
2017-11-24 10:16 ` Tobin C. Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511414131.12425.14.camel@gmail.com \
--to=kaiwan.billimoria@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox