From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: memccpy() gives inconsistent results on mmapped files
Date: Fri, 03 Dec 2004 18:00:09 +0000 [thread overview]
Message-ID: <20041203180009.GA12808@lucon.org> (raw)
In-Reply-To: <9880.1102044614@kao2.melbourne.sgi.com>
On Fri, Dec 03, 2004 at 07:22:41AM -0500, Jeff Hanson wrote:
> Christoph Hellwig wrote:
> >On Fri, Dec 03, 2004 at 02:30:14PM +1100, Keith Owens wrote:
> >
> >>Glenn Fowler of ATT reported that memccpy() gives inconsistent results
> >>on mmapped files. This was reported to SGI, but the bug is ia64
> >>generic, I get the same errors on a vanilla ia64 box.
> >>
> >>Glenn's test case follows, it has been tweaked to add a PREFAULT
> >>option. Prefaulting the input file makes memccpy work. The problem
> >>occurs on both glibc 2.2.4 and glibc 2.3.3.
> >
> >
> >Didn't Jes fix that long ago in SGIs glibc?
>
> Yes he did. For exactly the same customer with the same test code.
Can someone send me a patch?
Thanks.
H.J.
prev parent reply other threads:[~2004-12-03 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 3:30 memccpy() gives inconsistent results on mmapped files Keith Owens
2004-12-03 10:27 ` Christoph Hellwig
2004-12-03 12:22 ` Jeff Hanson
2004-12-03 18:00 ` H. J. Lu [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=20041203180009.GA12808@lucon.org \
--to=hjl@lucon.org \
--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