From: Kees Cook <keescook@chromium.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jann Horn <jannh@google.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] lkdtm: Check for SMEP clearing protections
Date: Tue, 26 Feb 2019 15:40:34 -0800 [thread overview]
Message-ID: <CAGXu5jJpeh5Ark4QG-UMUUkr-d+hWoBBb5eYzoGOCFXnW3xgkw@mail.gmail.com> (raw)
In-Reply-To: <20190226233647.28547-4-keescook@chromium.org>
On Tue, Feb 26, 2019 at 3:37 PM Kees Cook <keescook@chromium.org> wrote:
> + for (i = 0; i < 64; i++) {
> ...
> + }
> + if (i >= 256) {
> + pr_info("ok: cannot locate cr4 writing call gadget\n");
> + return;
> + }
*brown paper bag*
Argh. I changed the depth of that search at the last moment and now
it's mismatched. *sigh* I will send a v2 for this with it fixed.
--
Kees Cook
next prev parent reply other threads:[~2019-02-26 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 23:36 [PATCH 0/3] x86/asm: More pinning Kees Cook
2019-02-26 23:36 ` [PATCH 1/3] x86/asm: Pin sensitive CR0 bits Kees Cook
2019-02-27 10:44 ` Solar Designer
2019-02-27 19:45 ` Kees Cook
2019-02-26 23:36 ` [PATCH 2/3] x86/asm: Avoid taking an exception before cr4 restore Kees Cook
2019-02-26 23:36 ` [PATCH 3/3] lkdtm: Check for SMEP clearing protections Kees Cook
2019-02-26 23:40 ` Kees Cook [this message]
2019-02-26 23:45 ` [PATCH v2] " Kees Cook
2019-02-27 8:20 ` [PATCH 0/3] x86/asm: More pinning Greg KH
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=CAGXu5jJpeh5Ark4QG-UMUUkr-d+hWoBBb5eYzoGOCFXnW3xgkw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=jannh@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
/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).