From: Mark McLoughlin <markmc@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] preadv/pwritev data corruption on 32 bit
Date: Thu, 05 Nov 2009 14:55:15 -0500 [thread overview]
Message-ID: <1257450915.2885.34.camel@blaa> (raw)
Hey,
Just a heads up - on 32 bit hosts where qemu was using preadv and
pwritev, we were seeing data corruption due to file offset being
truncated:
https://bugzilla.redhat.com/533063
https://bugzilla.redhat.com/526549
The glibc headers fix is posted here:
http://sources.redhat.com/ml/libc-hacker/2009-11/msg00001.html
Cheers,
Mark.
next reply other threads:[~2009-11-05 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 19:55 Mark McLoughlin [this message]
2009-11-08 17:24 ` [Qemu-devel] preadv/pwritev data corruption on 32 bit Christoph Hellwig
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=1257450915.2885.34.camel@blaa \
--to=markmc@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).