From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA-32 emulation issues
Date: Wed, 08 Jan 2003 17:42:16 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805642@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805630@msgid-missing>
> I think this has been fixed in 2.5 already: the problem was that the
> x86 version of sys_open() ended up turning on the O_LARGEFILE flag,
> which was wrong (I think Andi Kleen pointed this out, originally).
> The fix was to add the sys32_open() wrapper. I don't recall if this
> has been added to 2.4.xx already. If not, it probably ought to be
> added.
I copied this change from 2.5 into 2.4:
# 02/12/03 davidm@tiger.hpl.hp.com 1.786.149.17
# ia64: For ia32 emulation, do not turn on O_LARGEFILE automatically
# on open(). Reported by Andi Kleen.
prev parent reply other threads:[~2003-01-08 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 21:27 [Linux-ia64] IA-32 emulation issues Arun Sharma
2003-01-02 21:18 ` David Mosberger
2003-01-02 23:31 ` Arun Sharma
2003-01-02 23:38 ` David Mosberger
2003-01-08 17:42 ` Bjorn Helgaas [this message]
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=marc-linux-ia64-105590709805642@msgid-missing \
--to=bjorn_helgaas@hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox