mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@redhat.com>
To: rusty@rustcorp.com.au, AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: mark.rutland@arm.com, keescook@chromium.org,
	kernel-hardening@lists.openwall.com,
	linux-kernel@vger.kernel.org
Subject: Re: module: extend 'rodata=off' boot cmdline parameter to module mappings
Date: Fri, 25 Nov 2016 00:48:22 -0500	[thread overview]
Message-ID: <20161125054822.GA2793@packer-debian-8-amd64.digitalocean.com> (raw)
In-Reply-To: <20161114061505.15238-1-takahiro.akashi@linaro.org>

+++ AKASHI Takahiro [14/11/16 15:15 +0900]:
>The current "rodata=off" parameter disables read-only kernel mappings
>under CONFIG_DEBUG_RODATA:
>    commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter
>    to disable read-only kernel mappings")
>
>This patch is a logical extension to module mappings ie. read-only mappings
>at module loading can be disabled even if CONFIG_DEBUG_SET_MODULE_RONX
>(mainly for debug use). Please note, however, that it only affects RO/RW
>permissions, keeping NX set.
>
>This is the first step to make CONFIG_DEBUG_SET_MODULE_RONX mandatory
>(always-on) in the future as CONFIG_DEBUG_RODATA on x86 and arm64.
>
>Suggested-by: and Acked-by: Mark Rutland <mark.rutland@arm.com>
>Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
>Reviewed-by: Kees Cook <keescook@chromium.org>
>Cc: Rusty Russell <rusty@rustcorp.com.au>

Hi Rusty, could I get an (n)ack for this patch? :-)

Thanks!

Jessica

  reply	other threads:[~2016-11-25  5:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  6:15 [PATCH v3] " AKASHI Takahiro
2016-11-25  5:48 ` Jessica Yu [this message]
2016-11-28  0:00   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2016-11-28  7:59 [PATCH v3] " Andreas Ziegler
2016-11-28  9:18 ` AKASHI Takahiro
2016-11-28 19:50   ` Jessica Yu
2016-10-21  1:13 [PATCH v2] " AKASHI Takahiro
2016-11-13  3:04 ` Jessica Yu
2016-11-14  6:12   ` AKASHI Takahiro

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=20161125054822.GA2793@packer-debian-8-amd64.digitalocean.com \
    --to=jeyu@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rusty@rustcorp.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome