mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Gall <tom_gall@vnet.ibm.com>
To: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: bug(?): SET_PERSONALITY 2.4.18-rc3
Date: Thu, 21 Feb 2002 20:50:08 -0600	[thread overview]
Message-ID: <3C75B1E0.ADC9B488@vnet.ibm.com> (raw)

Greetings,

While getting 2.4.18-rc[1|2] up and running on ppc64 the following bug
surfaced. Least I think it's a bug. You be the judge. If it's not, we'd
kinda like to know why not.

in fs/binfmt_elf.c I believe the following patch appears to be needed

------8<----------8<--------------------
diff -urN linuxppc64_2_4.bld-rc.borked/fs/binfmt_elf.c
linuxppc64_2_4.bld-rc/fs/binfmt_elf.c
--- linuxppc64_2_4.bld-rc.borked/fs/binfmt_elf.c        Wed Feb 20
13:32:56 2002
+++ linuxppc64_2_4.bld-rc/fs/binfmt_elf.c       Thu Feb 21 17:27:04 2002
@@ -568,6 +565,9 @@
			// printk(KERN_WARNING "ELF: Ambiguous type, using ELF\n");
			interpreter_type = INTERPRETER_ELF;
		}
+	} else {
+		/* Executables without an interpreter also need a personality  */
+		SET_PERSONALITY(elf_ex, ibcs2_interpreter);
	}

	/* OK, we are done with that, now set up the arg stuff,
----8<-------------8<------------------

otherwise a static application would be run without SET_PERSONALITY
being called, which On ppc64, very quickly leads to a bad day.

Regards,

Tom

-- 
Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey
Peace, Love &                  "Where's the ka-boom? There was
Linux Technology Center         supposed to be an earth
http://www.ibm.com/linux/ltc/   shattering ka-boom!"
(w) tom_gall@vnet.ibm.com       -- Marvin Martian
(w) 507-253-4558
(h) tgall@rochcivictheatre.org

             reply	other threads:[~2002-02-22  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  2:50 Tom Gall [this message]
2002-02-22  6:00 ` David S. Miller

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=3C75B1E0.ADC9B488@vnet.ibm.com \
    --to=tom_gall@vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®