From: "Tobin C. Harding" <me@tobin.cc>
To: kaiwan.billimoria@gmail.com
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] leaking_addresses: add 32-bit support
Date: Tue, 30 Jan 2018 16:11:38 +1100 [thread overview]
Message-ID: <20180130051138.GA4924@eros> (raw)
In-Reply-To: <1517283889.29097.1.camel@gmail.com>
On Tue, Jan 30, 2018 at 09:14:49AM +0530, kaiwan.billimoria@gmail.com wrote:
> Hi Tobin,
>
> On Mon, 2018-01-29 at 15:51 +1100, Tobin C. Harding wrote:
> > Currently script only supports x86_64 and ppc64. It would be nice to be
> > able to scan 32-bit machines also. We can add support for
> > 32-bit architectures by modifying how we check for false positives,
> > taking advantage of the page offset used by the kernel, and using the
> > correct regular expression.
> >
> > Support for 32-bit machines is enabled by the observation the kernel
> > addresses on 32-bit machines are larger than the page offset. We can
> > use this to filter false positives when scanning the kernel for leaking
> > addresses.
> >
> > Programmatic determination of the running architecture is not
> > immediately obvious. We therefore provide a flag to enable scanning of
> > 32-bit kernels. Also we can check the kernel config file for the offset
> > and if not found default to 0xc0000000. A command line option to parse
> > in the page offset is also provided. We do automatically detect
> > architecture if running on ix86.
> >
> > Add support for 32-bit kernels. Add a command line option for page
> > offset.
> >
> > Suggested-by: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> > ---
> >
> > The basis for this patch has been in development for a while by Kaiwan
> > but didn't get finished before the merge window opened. I'd like to
> > fast track this and get it to Linus this merge window (considering
> > Spectre/Meltdown). I have finished this work off and added the
> > Suggested-by tag. Kaiwan I hope you are not upset by this, extra
> > ordinary circumstances seemed to require this action.
> Definitely not; I understand and am glad you're on it a 100%. Apologies
> that I couldn't work on this right now.. will try and keep track too.
Thanks for the response.
Tobin
prev parent reply other threads:[~2018-01-30 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 4:51 [kernel-hardening] [PATCH] leaking_addresses: add 32-bit support Tobin C. Harding
2018-01-30 3:44 ` kaiwan.billimoria
2018-01-30 5:11 ` Tobin C. Harding [this message]
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=20180130051138.GA4924@eros \
--to=me@tobin.cc \
--cc=kaiwan.billimoria@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--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;
as well as URLs for NNTP newsgroup(s).