From: Kees Cook <keescook@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jinbum Park <jinb.park7@gmail.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Laura Abbott <labbott@redhat.com>
Subject: Re: [PATCH] mm: testcases for RODATA: fix config dependency
Date: Wed, 15 Feb 2017 14:12:27 -0800 [thread overview]
Message-ID: <CAGXu5jJ+KFOic1_JfD2iWfKdivKjteVqdybB7Jq=Eadcs72dwQ@mail.gmail.com> (raw)
In-Reply-To: <20170215130020.749e34e4d1e3d0789eb114f1@linux-foundation.org>
On Wed, Feb 15, 2017 at 1:00 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Fri, 10 Feb 2017 15:36:37 -0800 Kees Cook <keescook@chromium.org> wrote:
>
>> > config DEBUG_RODATA_TEST
>> > bool "Testcase for the marking rodata read-only"
>> > - depends on DEBUG_RODATA
>> > + depends on STRICT_KERNEL_RWX
>> > ---help---
>> > This option enables a testcase for the setting rodata read-only.
>>
>> Great, thanks!
>>
>> Acked-by: Kees Cook <keescook@chromium.org>
>>
>> Andrew, do you want to take this patch, since it applies on top of
>> "mm: add arch-independent testcases for RODATA", or do you want me to
>> take both patches into my KSPP tree which has the DEBUG_RODATA ->
>> STRICT_KERNEL_RWX renaming series?
>
> I staged this and mm-add-arch-independent-testcases-for-rodata.patch
> after linux-next and shall merge them after the STRICT_KERNEL_RWX
> rename has gone into mainline.
Awesome, thanks!
-Kees
--
Kees Cook
Pixel Security
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-02-15 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:16 [PATCH] mm: testcases for RODATA: fix config dependency Jinbum Park
2017-02-10 23:36 ` Kees Cook
2017-02-15 21:00 ` Andrew Morton
2017-02-15 22:12 ` Kees Cook [this message]
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='CAGXu5jJ+KFOic1_JfD2iWfKdivKjteVqdybB7Jq=Eadcs72dwQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=jinb.park7@gmail.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=valentinrothberg@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;
as well as URLs for NNTP newsgroup(s).