From: Thomas Gleixner <tglx@linutronix.de>
To: Vasily Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-hardening@lists.openwall.com,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH 2/3] use POISON_POINTER_DELTA for poison pointers
Date: Sun, 26 Jul 2015 20:42:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1507262041590.18576@nanos> (raw)
In-Reply-To: <20150726134519.GA1111@cachalot>
On Sun, 26 Jul 2015, Vasily Kulikov wrote:
> TIMER_ENTRY_STATIC and TAIL_MAPPING are defined as poison pointers which
> should point to nowhere. Redefine them using POISON_POINTER_DELTA arithmetics
> to make sure they really point to non-mappable area declared by the
> target architecture.
>
> Signed-off-by: Vasily Kulikov <segoon@openwall.com>
> ---
> include/linux/poison.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/poison.h b/include/linux/poison.h
> index ee697b9..a721bcd 100644
> --- a/include/linux/poison.h
> +++ b/include/linux/poison.h
> @@ -27,14 +27,14 @@
> * Magic number "tsta" to indicate a static timer initializer
> * for the object debugging code.
> */
> -#define TIMER_ENTRY_STATIC ((void *) 0x74737461)
> +#define TIMER_ENTRY_STATIC ((void *) 0x300 + POISON_POINTER_DELTA)
Acked-by: Thomas Gleixner <tglx@linutronix.de>
prev parent reply other threads:[~2015-07-26 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 13:43 [PATCH 1/3] fix LIST_POISON{1,2} offset Vasily Kulikov
2015-07-26 13:45 ` [PATCH 2/3] use POISON_POINTER_DELTA for poison pointers Vasily Kulikov
2015-07-26 13:46 ` [PATCH 3/3] remove not-used poison pointer macros Vasily Kulikov
2015-07-26 18:42 ` Thomas Gleixner [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=alpine.DEB.2.11.1507262041590.18576@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=segoon@openwall.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®