From: Michael Ellerman <mpe@ellerman.id.au>
To: Kees Cook <keescook@chromium.org>, Russell Currey <ruscur@russell.cc>
Cc: ajd@linux.ibm.com, kernel-hardening@lists.openwall.com,
npiggin@gmail.com, joel@jms.id.au, linuxppc-dev@lists.ozlabs.org,
dja@axtens.net
Subject: Re: [PATCH v4 0/4] Implement STRICT_MODULE_RWX for powerpc
Date: Wed, 30 Oct 2019 11:16:22 +1100 [thread overview]
Message-ID: <87zhhjf5pl.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <201910291601.F161FBBAB2@keescook>
Kees Cook <keescook@chromium.org> writes:
> On Mon, Oct 14, 2019 at 04:13:16PM +1100, Russell Currey wrote:
>> 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
>
> I continue to be excited about this work. :) Is there anything holding
> it back from landing in linux-next?
I had some concerns, which I stupidly posted in reply to v3:
https://lore.kernel.org/linuxppc-dev/87pnio5fva.fsf@mpe.ellerman.id.au/
cheers
next prev parent reply other threads:[~2019-10-30 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 5:13 [PATCH v4 0/4] Implement STRICT_MODULE_RWX for powerpc Russell Currey
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 [this message]
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=87zhhjf5pl.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ajd@linux.ibm.com \
--cc=dja@axtens.net \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=ruscur@russell.cc \
/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