LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Samium Gromoff <_deepfire@feelingofgreen.ru>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@ucw.cz>,
Valdis.Kletnieks@vt.edu, David Wagner <daw@cs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Define the EF_AS_NO_RANDOM e_flag bit
Date: Tue, 23 Jan 2007 15:50:18 -0500 [thread overview]
Message-ID: <20070123205017.GH29911@devserv.devel.redhat.com> (raw)
In-Reply-To: <877ivd8p42.wl@betelheise.deep.net>
On Tue, Jan 23, 2007 at 11:28:13PM +0300, Samium Gromoff wrote:
> Author: Samium Gromoff <deepfire@betelheise.deep.net>
> Date: Tue Jan 23 22:31:13 2007 +0300
>
> Define the ELF binary header flag EF_AS_NO_RANDOM
>
> EF_AS_NO_RANDOM should mean that the binary requests to not apply
> randomisation to address spaces of its processes.
>
> diff --git a/include/linux/elf.h b/include/linux/elf.h
> index 60713e6..58ebb47 100644
> --- a/include/linux/elf.h
> +++ b/include/linux/elf.h
> @@ -172,6 +172,8 @@ typedef struct elf64_sym {
>
> #define EI_NIDENT 16
>
> +#define EF_AS_NO_RANDOM 0x1 /* do not randomise the address space */
> +
You can't make up EF_* flags this way, they are arch specific, the LSB bit
(but many others too) are already used on many architectures.
E.g.:
elf/mt.h:#define EF_MT_CPU_MRISC 0x00000001 /* default */
elf/sparc.h:#define EF_SPARCV9_PSO 0x1 /* partial store ordering */
elf/bfin.h:#define EF_BFIN_PIC 0x00000001 /* -fpic */
elf/alpha.h:#define EF_ALPHA_32BIT 0x00000001
elf/mips.h:#define EF_MIPS_NOREORDER 0x00000001
elf/m68k.h:#define EF_M68K_CF_ISA_A_NODIV 0x01 /* ISA A except for div */
elf/sh.h:#define EF_SH1 1
elf/arm.h:#define EF_ARM_RELEXEC 0x01
elf/cris.h:#define EF_CRIS_UNDERSCORE 0x00000001
elf/ia64.h:#define EF_IA_64_TRAPNIL (1 << 0) /* Trap NIL pointer dereferences. */
elf/vax.h:#define EF_VAX_NONPIC 0x0001 /* Object contains non-PIC code */
elf/iq2000.h:#define EF_IQ2000_CPU_IQ2000 0x00000001 /* default */
elf/frv.h:#define EF_FRV_GPR_32 0x00000001 /* -mgpr-32 */
to name just a few.
Jakub
next prev parent reply other threads:[~2007-01-23 20:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 23:23 [PATCH] Undo some of the pseudo-security madness Samium Gromoff
2007-01-21 23:34 ` David Wagner
2007-01-22 0:36 ` Kyle Moffett
2007-01-22 1:53 ` Samium Gromoff
2007-02-24 9:40 ` Florian Weimer
2007-02-24 13:33 ` Samium Gromoff
2007-02-24 13:49 ` Florian Weimer
2007-01-22 15:20 ` Valdis.Kletnieks
2007-01-22 17:39 ` Samium Gromoff
2007-01-23 8:48 ` Pavel Machek
2007-01-23 14:03 ` Samium Gromoff
2007-01-23 15:41 ` Alan
2007-01-23 20:21 ` [PATCH 0/2] Mechanism to turn of ASR on a per-ELF binary basis Samium Gromoff
2007-01-23 20:28 ` [PATCH 1/2] Define the EF_AS_NO_RANDOM e_flag bit Samium Gromoff
2007-01-23 20:50 ` Jakub Jelinek [this message]
2007-01-23 21:06 ` Samium Gromoff
2007-01-23 21:16 ` Jakub Jelinek
2007-01-23 21:54 ` Samium Gromoff
2007-01-23 23:21 ` Samium Gromoff
2007-01-24 17:08 ` Pavel Machek
2007-01-29 1:18 ` Arjan van de Ven
2007-01-23 20:31 ` [PATCH 2/2] Make the EF_AS_NO_RANDOM e_flag bit disable PF_RANDOMIZE Samium Gromoff
2007-02-24 9:51 ` [PATCH] Undo some of the pseudo-security madness Florian Weimer
2007-02-24 13:36 ` Samium Gromoff
2007-01-31 9:59 ` Arjan van de Ven
2007-02-01 8:05 ` Florian Weimer
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=20070123205017.GH29911@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=_deepfire@feelingofgreen.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daw@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).