linux-kernel - Re: [PATCH] Make aout executables work again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <82e4877d0702100550ld369c8an2982a64dcc920169@mail.gmail.com>
Date:	Sat, 10 Feb 2007 08:50:06 -0500
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	joerg@...rops.han.de, dsd@...too.org, paulus@...ba.org,
	benh@...nel.crashing.org, lethal@...ux-sh.org
Subject: Re: [PATCH] Make aout executables work again

> 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?

Is there a reason why we specifically want to make a distinction
between binfmts having and not having VDSOs and do we want aout to
have the possibility of NOT having VDSO when a) It used to have it
unconditionally b) nothing special is needed in arch or common code to
have it and c) Not letting have it requires special arch-specific
code* ?

[*] I see the patch handles i386 and x86_64 - but I am not sure if
something similar will be needed for the other arches to allow aout
executables in absence of VDSO (powerpc, sh).

Parag
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/