public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Schoder <lists@gammarayburst.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ia32 binfmt problem with x86-64
Date: Tue, 27 Jun 2006 21:03:10 +0200	[thread overview]
Message-ID: <200606272103.10378.lists@gammarayburst.de> (raw)
In-Reply-To: <p73veqnt2ee.fsf@verdi.suse.de>

On Tuesday 27 June 2006 10:43, Andi Kleen wrote:
> lists@gammarayburst.de writes:
> > 
> > This all makes sense. But 64 bit and 32 bit apps should get the same
> > treatment right?
> 
> No - i386 behaves different here than x86-64.
> 
> x86-64 always had NX/PROT_EXEC (although not all CPUs have always enforced it)
> while i386 has lots of legacy binaries that don't know about it.

But then 32 bit apps should be handled in a less restrictive fashion
than 64 bit apps, no? And also probably only for binaries that do
not have the exec_stack flag at all.

What I fail to understand then is why a 64 bit application with the
exec_stack flag set gets read_implies_exec and a 32 bit application
also with the exec_stack flag set does not (this is also the only case
where the behavior differs).

--
Markus

  reply	other threads:[~2006-06-27 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 11:22 ia32 binfmt problem with x86-64 lists
2006-06-27  8:43 ` Andi Kleen
2006-06-27 19:03   ` Markus Schoder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-25 23:43 Markus Schoder
2006-06-26  8:30 ` Arjan van de Ven

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=200606272103.10378.lists@gammarayburst.de \
    --to=lists@gammarayburst.de \
    --cc=ak@suse.de \
    --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