From: Colin Vidal <colin@cvidal.org>
To: kernel-hardening@lists.openwall.com, "Reshetova,
Elena" <elena.reshetova@intel.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
David Windsor <dave@progbits.org>,
Kees Cook <keescook@chromium.org>,
Hans Liljestrand <ishkamiel@gmail.com>
Cc: Colin Vidal <colin@cvidal.org>
Subject: [kernel-hardening] [RFC 0/2] arm: implementation of HARDENED_ATOMIC
Date: Tue, 18 Oct 2016 16:59:19 +0200 [thread overview]
Message-ID: <1476802761-24340-1-git-send-email-colin@cvidal.org> (raw)
Hi,
This is the first attempt of HARDENED_ATOMIC port to arm arch.
About the fault handling I have some questions (perhaps some arm
expert are reading?):
- As the process that made the overflow is killed, the kernel will
not try to go to a fixup address when the exception is raised,
right ? Therefore, is still mandatory to add an entry in the
__extable section?
- In do_PrefetchAbort, I am unsure the code that follow the call to
hardened_atomic_overflow is needed: the process will be killed
anyways.
I take some freedom compared to PaX patch, especially by adding some
macro to expand functions in arm/include/asm/atomic.h.
The first patch is the modification I have done is generic part to
make it work.
Otherwise, I've been stuck by ccache. When I modify do_PrefetchAbort
in arm/mm/fault.c, ccache does not detect the update (even if the file
is recompiled by gcc). Therefore, when I boot the new compiled kernel,
the old version of do_PrefechAbort is called. I know do_PrefetchAbort
is somehow special, since called by assembly code, but is still
strange. Someone has already has this issue? The only way to solve it
is to flush the cache...
Thanks!
Colin
Colin Vidal (2):
Reordering / guard definition on atomic_*_wrap function in order to
avoid implicitly defined / redefined error on them, when
CONFIG_HARDENED_ATOMIC is unset.
arm: implementation for HARDENED_ATOMIC
arch/arm/Kconfig | 1 +
arch/arm/include/asm/atomic.h | 434 ++++++++++++++++++++++++++------------
arch/arm/mm/fault.c | 15 ++
include/asm-generic/atomic-long.h | 55 ++---
include/linux/atomic.h | 55 +++++
5 files changed, 405 insertions(+), 155 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-18 14:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:59 Colin Vidal [this message]
2016-10-18 14:59 ` [kernel-hardening] [RFC 1/2] Reordering / guard definition on atomic_*_wrap function in order to avoid implicitly defined / redefined error on them, when CONFIG_HARDENED_ATOMIC is unset Colin Vidal
2016-10-18 16:04 ` Vaishali Thakkar
2016-10-19 8:48 ` Colin Vidal
2016-10-19 8:21 ` [kernel-hardening] " Reshetova, Elena
2016-10-19 8:31 ` Greg KH
2016-10-19 8:58 ` Colin Vidal
2016-10-19 9:16 ` Greg KH
2016-10-18 14:59 ` [kernel-hardening] [RFC 2/2] arm: implementation for HARDENED_ATOMIC Colin Vidal
2016-10-18 21:29 ` [kernel-hardening] " Kees Cook
2016-10-19 8:45 ` Colin Vidal
2016-10-19 20:11 ` Kees Cook
2016-10-20 5:58 ` AKASHI Takahiro
2016-10-20 8:30 ` Colin Vidal
2016-10-25 9:18 ` AKASHI Takahiro
2016-10-25 15:02 ` Colin Vidal
2016-10-26 7:24 ` AKASHI Takahiro
2016-10-26 8:20 ` Colin Vidal
2016-10-27 11:08 ` Mark Rutland
2016-10-27 21:37 ` Kees Cook
2016-10-27 13:24 ` [kernel-hardening] " Mark Rutland
2016-10-28 5:18 ` AKASHI Takahiro
2016-10-28 8:33 ` Colin Vidal
2016-10-28 10:20 ` Mark Rutland
2016-10-28 10:59 ` David Windsor
2016-10-21 7:47 ` [kernel-hardening] Re: [RFC 0/2] arm: implementation of HARDENED_ATOMIC AKASHI Takahiro
2016-10-27 10:32 ` [kernel-hardening] " Mark Rutland
2016-10-27 12:45 ` David Windsor
2016-10-27 13:53 ` Mark Rutland
2016-10-27 14:10 ` David Windsor
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=1476802761-24340-1-git-send-email-colin@cvidal.org \
--to=colin@cvidal.org \
--cc=dave@progbits.org \
--cc=elena.reshetova@intel.com \
--cc=ishkamiel@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=takahiro.akashi@linaro.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 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.