From: Markus Schoder <lists@gammarayburst.de>
To: linux-kernel@vger.kernel.org
Subject: ia32 binfmt problem with x86-64
Date: Mon, 26 Jun 2006 01:43:16 +0200 [thread overview]
Message-ID: <200606260143.16362.lists@gammarayburst.de> (raw)
The 32 bit emulation for x86-64 has the following in
arch/x86_64/ia32/ia32_binfmt.c:
#define elf_read_implies_exec(ex, have_pt_gnu_stack) \
(!(have_pt_gnu_stack))
I guess it should be same definition as in include/asm-i386/elf.h and
include/asm-x86_64/elf.h instead:
#define elf_read_implies_exec(ex, executable_stack) \
(executable_stack != EXSTACK_DISABLE_X)
>From the usage in fs/binfmt_elf.c it looks like the semantics of that
macro changed slightly but was not fixed in all places (ia64 seems to
have a similar problem from the looks of it).
The current behavior leads to 32 bit executables not setting the
READ_IMPLIES_EXEC personality when they are marked as requiring an
executable stack (64 bit executables do however).
--
Markus
next reply other threads:[~2006-06-25 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 23:43 Markus Schoder [this message]
2006-06-26 8:30 ` ia32 binfmt problem with x86-64 Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 11:22 lists
2006-06-27 8:43 ` Andi Kleen
2006-06-27 19:03 ` Markus Schoder
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=200606260143.16362.lists@gammarayburst.de \
--to=lists@gammarayburst.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 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.