From: Russell Currey <ruscur@russell.cc>
To: linuxppc-dev@lists.ozlabs.org
Cc: ajd@linux.ibm.com, kernel-hardening@lists.openwall.com,
npiggin@gmail.com, joel@jms.id.au,
Russell Currey <ruscur@russell.cc>,
dja@axtens.net
Subject: [PATCH v4 0/4] Implement STRICT_MODULE_RWX for powerpc
Date: Mon, 14 Oct 2019 16:13:16 +1100 [thread overview]
Message-ID: <20191014051320.158682-1-ruscur@russell.cc> (raw)
v3 cover letter here:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-October/198023.html
Only minimal changes since then:
- patch 2/4 commit message update thanks to Andrew Donnellan
- patch 3/4 made neater thanks to Christophe Leroy
- patch 3/4 updated Kconfig description thanks to Daniel Axtens
Russell Currey (4):
powerpc/mm: Implement set_memory() routines
powerpc/kprobes: Mark newly allocated probes as RO
powerpc/mm/ptdump: debugfs handler for W+X checks at runtime
powerpc: Enable STRICT_MODULE_RWX
arch/powerpc/Kconfig | 2 +
arch/powerpc/Kconfig.debug | 6 ++-
arch/powerpc/configs/skiroot_defconfig | 1 +
arch/powerpc/include/asm/set_memory.h | 32 ++++++++++++++
arch/powerpc/kernel/kprobes.c | 3 ++
arch/powerpc/mm/Makefile | 1 +
arch/powerpc/mm/pageattr.c | 60 ++++++++++++++++++++++++++
arch/powerpc/mm/ptdump/ptdump.c | 21 ++++++++-
8 files changed, 123 insertions(+), 3 deletions(-)
create mode 100644 arch/powerpc/include/asm/set_memory.h
create mode 100644 arch/powerpc/mm/pageattr.c
--
2.23.0
next reply other threads:[~2019-10-14 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 5:13 Russell Currey [this message]
2019-10-14 5:13 ` [PATCH v4 1/4] powerpc/mm: Implement set_memory() routines Russell Currey
2019-10-14 5:13 ` [PATCH v4 2/4] powerpc/kprobes: Mark newly allocated probes as RO Russell Currey
2019-10-14 5:13 ` [PATCH v4 3/4] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime Russell Currey
2019-10-14 5:13 ` [PATCH v4 4/4] powerpc: Enable STRICT_MODULE_RWX Russell Currey
2019-10-29 23:02 ` [PATCH v4 0/4] Implement STRICT_MODULE_RWX for powerpc Kees Cook
2019-10-30 0:16 ` Michael Ellerman
2019-10-30 18:43 ` Kees Cook
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=20191014051320.158682-1-ruscur@russell.cc \
--to=ruscur@russell.cc \
--cc=ajd@linux.ibm.com \
--cc=dja@axtens.net \
--cc=joel@jms.id.au \
--cc=kernel-hardening@lists.openwall.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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: 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