All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Arijit Das <Arijit.Das@synopsys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Shared library holes in x86_64
Date: Mon, 3 Oct 2005 03:18:13 -0400	[thread overview]
Message-ID: <20051003071813.GI8983@devserv.devel.redhat.com> (raw)
In-Reply-To: <7EC22963812B4F40AE780CF2F140AFE916835A@IN01WEMBX1.internal.synopsys.com>

On Mon, Oct 03, 2005 at 12:00:05PM +0530, Arijit Das wrote:
> If I strace a "/bin/sleep 23" command in a RHAS3.0/x86-AMD64 machine, I
> see that holes are being created in some of the mapped shared libraries
> using the mprotect system call like this:

I explained it 3 days ago, so once again:
x86-64 binaries and shared libraries are required to handle page sizes up
to 1MB and as RE and RW segments can't be on the same page, this means they
must not share the same 1MB page.
Just google for ELF_MAXPAGESIZE or look at the libraries using readelf -Wl.

	Jakub

       reply	other threads:[~2005-10-03  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7EC22963812B4F40AE780CF2F140AFE916835A@IN01WEMBX1.internal.synopsys.com>
2005-10-03  7:18 ` Jakub Jelinek [this message]
2005-10-03  7:27 Shared library holes in x86_64 Arijit Das

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=20051003071813.GI8983@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=Arijit.Das@synopsys.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.