From: Richard Henderson <rth@redhat.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: torvalds@transmeta.com, alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: alpha 2.4.13: fix taso osf emulation
Date: Fri, 26 Oct 2001 10:03:46 -0700 [thread overview]
Message-ID: <20011026100346.C1663@redhat.com> (raw)
In-Reply-To: <20011026013101.A1404@redhat.com> <Pine.GSO.3.96.1011026113847.14048A-100000@delta.ds2.pg.gda.pl>
In-Reply-To: <Pine.GSO.3.96.1011026113847.14048A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Oct 26, 2001 at 12:01:10PM +0200
On Fri, Oct 26, 2001 at 12:01:10PM +0200, Maciej W. Rozycki wrote:
> The following trivial patch reportedly fixes OSF/1 programs using 31-bit
> addressing. It's already present in the -ac tree; I guess it just got
> lost during a merge. It applies fine to 2.4.13.
This is the patch that Jay Estabrook forwarded me that I rejected
in favour of writing a special arch_get_unmapped_area.
> It used to do so. It breaks things such as dynamic linking of shared
> objects linked at high load address.
Err, how?
> It breaks mmap() in principle, as it shouldn't fail when invoked with
> a non-zero, non-MAP_FIXED, invalid address if there is still address
> space available elsewhere.
No, it doesn't. Or rather, it only does if you only bothered
to search once. IMO one should search thrice: once at addr,
once at TASK_UNMAPPED_BASE, and once at PAGE_SIZE.
r~
next prev parent reply other threads:[~2001-10-26 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 8:31 alpha 2.4.13: fix taso osf emulation Richard Henderson
2001-10-26 10:01 ` Maciej W. Rozycki
2001-10-26 10:45 ` Ivan Kokshaysky
2001-10-26 17:11 ` Richard Henderson
2001-10-29 16:35 ` Ivan Kokshaysky
2001-10-29 17:21 ` Richard Henderson
2001-10-26 17:03 ` Richard Henderson [this message]
2001-10-26 18:25 ` Maciej W. Rozycki
2001-10-28 9:38 ` Module loading and Kernel crash Anand Ashok Kulkarni
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=20011026100346.C1663@redhat.com \
--to=rth@redhat.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=torvalds@transmeta.com \
/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.