linux-kernel - Re: [PATCH 2/3] use POISON_POINTER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 26 Jul 2015 20:42:16 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Vasily Kulikov <segoon@...nwall.com>
cc:	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel-hardening@...ts.openwall.com,
	"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH 2/3] use POISON_POINTER_DELTA for poison pointers

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@...nwall.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@...utronix.de>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/