mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: me@tobin.cc, kaiwan.billimoria@gmail.com
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	Alexander Kapshuk <alexander.kapshuk@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-hardening@lists.openwall.com
Subject: [PATCH 0/5] leaking_addresses: support 5 page table level
Date: Thu,  7 Dec 2017 15:32:20 +1100	[thread overview]
Message-ID: <1512621145-4783-1-git-send-email-me@tobin.cc> (raw)

This set adds support for 5 page table levels on x86_64.

Patch 1 and 2 are clean up.

Patch 3 adds checking vsyscall memory region instead of just first and
last address.

Patch 4 adds support for locating and parsing the current kernel config
file.  It feels like this may be re-inventing the wheel (also the
implementation is not as thorough as scripts/extract-ikconfig?) Much of
the code for this has been posted on LKML a few times now by Kaiwan
Billimoria. As such, it uses the new Co-Developed-by tag.

Patch 5 adds the 5 page table levels stuff. It is trivial once we have a
value from CONFIG_PGTABLE_LEVELS. Just set the regular expression
accordingly.

Perl tips, and code style tips in general, most appreciated.

As usual, any kernel development protocol tips also most
appreciated. Both Kaiwan and myself are pretty new around here, feel
free to give us a kick if we need it.

thanks,
Tobin.

Tobin C. Harding (5):
  leaking_addresses: remove command examples
  leaking_addresses: indent dependant options
  leaking_addresses: add range check for vsyscall memory
  leaking_addresses: add support for kernel config file
  leaking_addresses: add support for 5 page table levels

 scripts/leaking_addresses.pl | 169 +++++++++++++++++++++++++++++++++++--------
 1 file changed, 137 insertions(+), 32 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-12-07  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  4:32 Tobin C. Harding [this message]
2017-12-07  4:32 ` [PATCH 1/5] leaking_addresses: remove command examples Tobin C. Harding
2017-12-07  4:32 ` [PATCH 2/5] leaking_addresses: indent dependant options Tobin C. Harding
2017-12-07  4:32 ` [PATCH 3/5] leaking_addresses: add range check for vsyscall memory Tobin C. Harding
2017-12-07  4:32 ` [PATCH 4/5] leaking_addresses: add support for kernel config file Tobin C. Harding
2017-12-08  1:55   ` Kaiwan N Billimoria
2017-12-07  4:32 ` [PATCH 5/5] leaking_addresses: add support for 5 page table levels 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=1512621145-4783-1-git-send-email-me@tobin.cc \
    --to=me@tobin.cc \
    --cc=alexander.kapshuk@gmail.com \
    --cc=kaiwan.billimoria@gmail.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®