From: Andi Kleen <ak@suse.de>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
joerg@hydrops.han.de, dsd@gentoo.org, paulus@samba.org,
benh@kernel.crashing.org, lethal@linux-sh.org
Subject: Re: [PATCH] Make aout executables work again
Date: 10 Feb 2007 13:58:13 +0100 [thread overview]
Message-ID: <p73y7n6goey.fsf@bingen.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0702092100540.3984@localhost.localdomain>
Parag Warudkar <parag.warudkar@gmail.com> writes:
> This a reworked, replacement version of
> x86-fix-vdso-mapping-for-aout-executables-* series of patches in -mm.
>
> 1) Define arch_setup_additional_pages() as weak in linux/interp.h
> 2) Include linux/interp.h in appropriate places
> 3) Conditionally call arch_setup_additional_pages() from binfmt_*.c if
> the arch defines it
> 4) EXPORT_SYMBOL_GPL(arch_setup_additional_pages) for all x86{64},
> powerpc, sh - binfmt_aout can be built as module
> 5) Get rid of ARCH_HAS_SETUP_ADDITIONAL_PAGES from various places
> 6) For x86_64 - define and export arch_setup_additional_pages as a
> wrapper over syscall32_setup_pages, call it from ia32_aout.c
>
> Fully tested on x86. (Compile, boot and run the aout binary at
> http://ftp.funet.fi/pub/Linux/bin/as86.tar.Z). Other arches - changes
> are minimal but still I'll appreciate if someone tests them.
I already fixed this in a different way -- just use the stack
trampoline on a.out
Can you double check
ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/aout-no-vdso
works for you?
-Andi
next prev parent reply other threads:[~2007-02-10 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 2:31 [PATCH] Make aout executables work again Parag Warudkar
2007-02-10 12:58 ` Andi Kleen [this message]
2007-02-10 13:50 ` Parag Warudkar
2007-02-10 14:24 ` Andi Kleen
2007-02-10 14:41 ` Parag Warudkar
2007-02-10 15:12 ` Andi Kleen
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=p73y7n6goey.fsf@bingen.suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dsd@gentoo.org \
--cc=joerg@hydrops.han.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=paulus@samba.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