public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: keescook@chromium.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: kaslr should avoid setup_data region
Date: Thu, 24 Apr 2014 10:35:44 +0800	[thread overview]
Message-ID: <20140424023544.GA2180@darkstar.nay.redhat.com> (raw)

Hello Kees

I'm worrying that setup_data regions could be overwitten by randomize
kernel base. Would you like to fix it in kaslr code?

One problem is there could be a lot of setup_data regions but current
mem_avoid is an fixed array.

Thanks
Dave

             reply	other threads:[~2014-04-24  2:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  2:35 Dave Young [this message]
2014-04-24  2:43 ` kaslr should avoid setup_data region Kees Cook
2014-04-24  2:50   ` Dave Young
2014-04-24 22:50     ` Kees Cook
2014-04-24 23:46       ` H. Peter Anvin
2014-04-25  9:44       ` Dave Young
2014-05-05  8:58       ` Dave Young
2014-05-08  9:46       ` Dave Young
2014-05-08 19:31         ` Kees Cook
2014-05-09  3:21           ` Dave Young

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=20140424023544.GA2180@darkstar.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    /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