mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "PaX Team" <pageexec@freemail.hu>
To: Kees Cook <keescook@chromium.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Laura Abbott <labbott@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lkdtm: add test for executing .rodata
Date: Tue, 23 Feb 2016 23:00:23 +0100	[thread overview]
Message-ID: <56CCD677.1316.1C5E89E6@pageexec.freemail.hu> (raw)
In-Reply-To: <CAGXu5jLhZMMS_StwD_2yDPoF1tL1OwfBrfo3n217RYnrHkwMww@mail.gmail.com>

On 23 Feb 2016 at 12:53, Kees Cook wrote:

> I prefer using all the "regular" mechanisms so that I really know I'm
> exercising the actual case I want to be testing. (i.e. I don't want to
> bypass the linker.)
> 
> If only there were some way to filter gcc output, like with plugins. ;)

plugins can set/override section flags, initify and constify both do in
fact but i guess that's little help for your generic case that has to
work without them as well.

  reply	other threads:[~2016-02-23 22:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 21:49 Kees Cook
2016-02-17  1:06 ` Laura Abbott
2016-02-17 20:29   ` Kees Cook
2016-02-17 21:06     ` Kees Cook
2016-02-18 10:32     ` PaX Team
2016-02-18 11:34       ` Ard Biesheuvel
2016-02-18 11:55         ` Ard Biesheuvel
2016-02-18 12:07         ` Arnd Bergmann
2016-02-18 12:46           ` Ard Biesheuvel
2016-02-18 20:04             ` Kees Cook
2016-02-18 21:27         ` PaX Team
2016-02-22 20:46           ` Kees Cook
2016-02-22 23:21             ` PaX Team
2016-02-23 20:53               ` Kees Cook
2016-02-23 22:00                 ` PaX Team [this message]
2016-02-23 22:02                   ` Kees Cook
2016-02-23 20:31             ` [kernel-hardening] " David Brown
2016-02-23 20:51               ` Kees Cook
2016-02-17 21:44 ` Arnd Bergmann
2016-02-17 21:45   ` Arnd Bergmann

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=56CCD677.1316.1C5E89E6@pageexec.freemail.hu \
    --to=pageexec@freemail.hu \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.linton@arm.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®