From: Laura Abbott <labbott@redhat.com> To: Alexander Popov <alex.popov@linux.com>, Kees Cook <keescook@chromium.org>, Mark Rutland <mark.rutland@arm.com>, Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Laura Abbott <labbott@redhat.com>, kernel-hardening@lists.openwall.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] Stackleak for arm64 Date: Tue, 20 Feb 2018 17:13:01 -0800 [thread overview] Message-ID: <20180221011303.20392-1-labbott@redhat.com> (raw) In-Reply-To: <dc76a745-3fa7-4023-dcc1-3df18c9461a6@redhat.com> This is the arm64 version of the STACKLEAK plugin originall from grsecurity. See https://marc.info/?l=kernel-hardening&m=151880470609808 for the full x86 version. This is based on top of Kees' branch for stackleak and has been cleaned up to use a few macros from that branch. Comments welcome, if there are no major objections Kees will queue this up to get some CI testing. This passed both of the LKDTM tests. Laura Abbott (2): stackleak: Update for arm64 arm64: Clear the stack arch/arm64/Kconfig | 1 + arch/arm64/include/asm/processor.h | 6 ++ arch/arm64/kernel/asm-offsets.c | 3 + arch/arm64/kernel/entry.S | 108 +++++++++++++++++++++++++++++++++ arch/arm64/kernel/process.c | 16 +++++ drivers/firmware/efi/libstub/Makefile | 3 +- scripts/Makefile.gcc-plugins | 5 +- scripts/gcc-plugins/stackleak_plugin.c | 5 ++ 8 files changed, 145 insertions(+), 2 deletions(-) -- 2.14.3
WARNING: multiple messages have this Message-ID (diff)
From: labbott@redhat.com (Laura Abbott) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/2] Stackleak for arm64 Date: Tue, 20 Feb 2018 17:13:01 -0800 [thread overview] Message-ID: <20180221011303.20392-1-labbott@redhat.com> (raw) In-Reply-To: <dc76a745-3fa7-4023-dcc1-3df18c9461a6@redhat.com> This is the arm64 version of the STACKLEAK plugin originall from grsecurity. See https://marc.info/?l=kernel-hardening&m=151880470609808 for the full x86 version. This is based on top of Kees' branch for stackleak and has been cleaned up to use a few macros from that branch. Comments welcome, if there are no major objections Kees will queue this up to get some CI testing. This passed both of the LKDTM tests. Laura Abbott (2): stackleak: Update for arm64 arm64: Clear the stack arch/arm64/Kconfig | 1 + arch/arm64/include/asm/processor.h | 6 ++ arch/arm64/kernel/asm-offsets.c | 3 + arch/arm64/kernel/entry.S | 108 +++++++++++++++++++++++++++++++++ arch/arm64/kernel/process.c | 16 +++++ drivers/firmware/efi/libstub/Makefile | 3 +- scripts/Makefile.gcc-plugins | 5 +- scripts/gcc-plugins/stackleak_plugin.c | 5 ++ 8 files changed, 145 insertions(+), 2 deletions(-) -- 2.14.3
next prev parent reply other threads:[~2018-02-21 1:13 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-16 18:10 [PATCH RFC v8 0/6] Introduce the STACKLEAK feature and a test for it Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 1/6] x86/entry: Add STACKLEAK erasing the kernel stack at the end of syscalls Alexander Popov 2018-02-21 13:24 ` Borislav Petkov 2018-02-21 21:49 ` Alexander Popov 2018-02-22 19:14 ` Borislav Petkov 2018-02-22 20:24 ` Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 2/6] gcc-plugins: Add STACKLEAK plugin for tracking the kernel stack Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 3/6] x86/entry: Erase kernel stack in syscall_trace_enter() Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 4/6] lkdtm: Add a test for STACKLEAK Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 5/6] fs/proc: Show STACKLEAK metrics in the /proc file system Alexander Popov 2018-02-16 18:10 ` [PATCH RFC v8 6/6] doc: self-protection: Add information about STACKLEAK feature Alexander Popov 2018-02-20 10:29 ` [PATCH RFC v8 0/6] Introduce the STACKLEAK feature and a test for it Alexander Popov 2018-02-20 23:17 ` Kees Cook 2018-02-20 23:33 ` Laura Abbott 2018-02-21 1:13 ` Laura Abbott [this message] 2018-02-21 1:13 ` [PATCH 0/2] Stackleak for arm64 Laura Abbott 2018-02-21 1:13 ` [PATCH 1/2] stackleak: Update " Laura Abbott 2018-02-21 1:13 ` Laura Abbott 2018-02-22 16:58 ` Will Deacon 2018-02-22 16:58 ` Will Deacon 2018-02-22 19:22 ` Alexander Popov 2018-02-22 19:22 ` Alexander Popov 2018-02-27 10:21 ` Richard Sandiford 2018-02-27 10:21 ` Richard Sandiford 2018-02-27 10:21 ` Richard Sandiford 2018-02-28 15:09 ` Alexander Popov 2018-02-28 15:09 ` Alexander Popov 2018-03-01 10:33 ` Richard Sandiford 2018-03-01 10:33 ` Richard Sandiford 2018-03-01 10:33 ` Richard Sandiford 2018-03-02 11:14 ` Alexander Popov 2018-03-02 11:14 ` Alexander Popov 2018-02-22 19:38 ` Laura Abbott 2018-02-22 19:38 ` Laura Abbott 2018-02-21 1:13 ` [PATCH 2/2] arm64: Clear the stack Laura Abbott 2018-02-21 1:13 ` Laura Abbott 2018-02-21 15:38 ` Mark Rutland 2018-02-21 15:38 ` Mark Rutland 2018-02-21 23:53 ` Laura Abbott 2018-02-21 23:53 ` Laura Abbott 2018-02-22 1:35 ` Laura Abbott 2018-02-22 1:35 ` Laura Abbott 2018-02-21 14:48 ` [PATCH 0/2] Stackleak for arm64 Alexander Popov 2018-02-21 14:48 ` Alexander Popov 2018-02-21 10:05 ` [PATCH RFC v8 0/6] Introduce the STACKLEAK feature and a test for it Borislav Petkov 2018-02-21 15:09 ` Alexander Popov 2018-02-21 14:43 ` Alexander Popov 2018-02-22 1:43 ` Laura Abbott 2018-02-22 23:14 ` [PATCH 0/2] Update stackleak for gcc-8 Laura Abbott 2018-02-22 23:14 ` [PATCH 1/2] gcc-plugins: Update cgraph_create_edge " Laura Abbott 2018-02-22 23:40 ` Kees Cook 2018-02-23 17:30 ` Laura Abbott 2018-02-24 12:36 ` Alexander Popov 2018-02-22 23:14 ` [PATCH 2/2] gcc-plugins: stackleak: Update " Laura Abbott 2018-02-24 14:04 ` Alexander Popov 2018-02-26 21:51 ` Laura Abbott 2018-02-27 10:30 ` Richard Sandiford 2018-02-28 10:27 ` Alexander Popov 2018-02-22 23:43 ` [PATCH 0/2] Update stackleak " Kees Cook 2018-04-06 14:22 [PATCH v11 0/6] Introduce the STACKLEAK feature and a test for it Alexander Popov 2018-05-02 20:33 ` [PATCH 0/2] Stackleak for arm64 Laura Abbott 2018-05-02 20:33 ` Laura Abbott 2018-07-11 20:36 [PATCH v14 0/6] Introduce the STACKLEAK feature and a test for it Alexander Popov 2018-07-18 21:10 ` [PATCH 0/2] Stackleak for arm64 Laura Abbott 2018-07-18 21:10 ` Laura Abbott
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=20180221011303.20392-1-labbott@redhat.com \ --to=labbott@redhat.com \ --cc=alex.popov@linux.com \ --cc=ard.biesheuvel@linaro.org \ --cc=keescook@chromium.org \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.