From: Vasily Kulikov <segoon@openwall.com>
To: Solar Designer <solar@openwall.com>
Cc: Wen Xu <hotdog3645@gmail.com>,
oss-security@lists.openwall.com,
kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: Linux kernel pointer poisoning (was: CVE request for a fixed bug existed in all versions of linux kernel from KeenTeam)
Date: Thu, 7 May 2015 12:37:51 +0300 [thread overview]
Message-ID: <20150507093751.GA18746@cachalot> (raw)
In-Reply-To: <20150507093639.GA4522@cachalot>
On Thu, May 07, 2015 at 12:36 +0300, Vasily Kulikov wrote:
> b) how to check for an insane POISON_POINTER() arg in case of
> TIMER_ENTRY_STATIC (and such)? The current implementation of
> POISON_POINTER() fails as following:
>
> mm/page_alloc.c: In function 'free_pages_prepare':
> mm/page_alloc.c:840:23: error: call to '__compiletime_assert_840' declared with attribute error: BUILD_BUG_ON failed: 0x0111400 >= POISON_AREA_SIZE
Sorry, I've copied a wrong error message. The right one is as
following:
kernel/irq/spurious.c:23:8: error: braced-group within expression allowed only inside a function
--
Vasily Kulikov
http://www.openwall.com - bringing security into open computing environments
prev parent reply other threads:[~2015-05-07 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADOUnBK=jW36v6X2Q6EXLL35Wxqait7cWJR-adCFwRaMJtucPQ@mail.gmail.com>
[not found] ` <20150502125329.GA6820@openwall.com>
2015-05-07 9:36 ` [kernel-hardening] Linux kernel pointer poisoning (was: CVE request for a fixed bug existed in all versions of linux kernel from KeenTeam) Vasily Kulikov
2015-05-07 9:37 ` Vasily Kulikov [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=20150507093751.GA18746@cachalot \
--to=segoon@openwall.com \
--cc=hotdog3645@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=oss-security@lists.openwall.com \
--cc=solar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.