public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: mike@navi.cx
Cc: Ulrich Drepper <drepper@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Potential bug in fs/binfmt_elf.c?
Date: 07 Mar 2004 16:55:33 -0700	[thread overview]
Message-ID: <m1brn8us96.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1078607410.10313.7.camel@linux.littlegreen>

Mike Hearn <mike@navi.cx> writes:

> On Sat, 2004-03-06 at 18:46, Ulrich Drepper wrote:
> > Show an example of what the file looks like.  Just the ELF program
> > header (readelf -l output).
> 
> I can send the linker script and source file on request. They are
> probably a bit buggy, this isn't an area I know much about. The binutils
> guys seemed to think it should work however.
> 
> thanks -mike
> 
> 
> Elf file type is EXEC (Executable file)
> Entry point 0x818
> There are 6 program headers, starting at offset 52
>  
> Program Headers:
>   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
>   PHDR           0x000034 0x00000034 0x00000034 0x000c0 0x000c0 R   0x4
>   INTERP         0x000400 0x00000400 0x00000400 0x00034 0x00034 R   0x4
>       [Requesting program interpreter: /lib/ld-linux.so.2]
>   LOAD           0x000000 0x00000000 0x00000000 0x00bc4 0x00bc4 R E 0x1000
>   LOAD           0x000bc4 0x00000bc4 0x00000bc4 0x00150 0x00154 RW  0x1000
>   DYNAMIC        0x000bd0 0x00000bd0 0x00000bd0 0x00108 0x00108 RW  0x4
>   LOAD           0x001000 0x00400000 0x00400000 0x00000 0x10000000 R   0x1000

That last PT_LOAD segment looks like pure nonsense.  What is the purpose
of allocating 256MB of read-only zeros?

Eric

  parent reply	other threads:[~2004-03-08  0:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 17:38 Potential bug in fs/binfmt_elf.c? Mike Hearn
2004-03-05 18:28 ` John Reiser
2004-03-06 18:46 ` Ulrich Drepper
2004-03-06 21:10   ` Mike Hearn
2004-03-07  6:11     ` Ulrich Drepper
2004-03-07  9:58       ` Mike Hearn
2004-03-07 10:46         ` Ulrich Drepper
2004-03-07 11:53           ` Mike Hearn
2004-03-07 21:32             ` Ulrich Drepper
2004-03-07 23:55     ` Eric W. Biederman [this message]
2004-03-08  5:57       ` John Reiser
2004-03-08  8:06         ` Jakub Jelinek
2004-03-11  6:17           ` [PATCH] binfmt_elf.c allow .bss with no access (p---) John Reiser
2004-03-11 14:23             ` Mike Hearn
2004-03-11 19:18               ` John Reiser
2004-03-12 16:42                 ` Mike Hearn
     [not found]             ` <20040412185317.79ac7d7d.akpm@osdl.org>
2004-04-13 17:33               ` John Reiser

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=m1brn8us96.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@navi.cx \
    /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