All of lore.kernel.org
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] GNU_STACK policy problem
Date: Mon, 22 Aug 2011 13:41:38 +0400	[thread overview]
Message-ID: <20110822094138.GA13710@openwall.com> (raw)
In-Reply-To: <20110822093405.GA2450@albatros>

Vasiliy,

On Mon, Aug 22, 2011 at 01:34:05PM +0400, Vasiliy Kulikov wrote:
> Looking into ELF documentation:
> 
> In MIPS, SPARC no AT_FLAGS bits are used currently.  And "bits under the
> 0xff000000 mask are reserved for system semantics."
> 
> In IA-32 and PPC no bits are used.  No "system" flags are mentioned.
> 
> 
> I didn't find any definition of "system semantics", I guess it means any
> non-standard usage on local system.  Probably we should use these bits.

Yes, using some of those reserved bits (even if reserved on other archs
only) makes sense to me.

Your changes look good to me - at least good enough to bring a
discussion up on LKML if you choose to do so despite of the NAK
expectation.  As discussed off-list, I think it's OK to try.

Thanks,

Alexander

      reply	other threads:[~2011-08-22  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 19:48 [kernel-hardening] GNU_STACK policy problem Vasiliy Kulikov
2011-07-21 13:03 ` [kernel-hardening] " Vasiliy Kulikov
2011-07-23 15:06 ` [kernel-hardening] " Solar Designer
2011-07-24  8:39   ` Vasiliy Kulikov
2011-07-24 14:06     ` Solar Designer
2011-07-26 12:07       ` Vasiliy Kulikov
2011-07-23 15:37 ` Solar Designer
2011-08-22  9:34   ` Vasiliy Kulikov
2011-08-22  9:41     ` Solar Designer [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=20110822094138.GA13710@openwall.com \
    --to=solar@openwall.com \
    --cc=kernel-hardening@lists.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.