From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, rtc@gmx.de
Subject: Re: [PATCH/RFC] pass dio_complete proper offset from finished_one_bio
Date: Tue, 28 Nov 2006 08:09:50 -0600 [thread overview]
Message-ID: <456C432E.2050601@redhat.com> (raw)
In-Reply-To: <45691753.60500@redhat.com>
Eric Sandeen wrote:
> We saw problems w/ xfs doing AIO+DIO into a sparse file.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217098
>
> It seemed that xfs was doing "extent conversion" at the wrong offsets, so
> written regions came up as unwritten (zeros) and stale data was exposed
> in the region after the write. Thanks to Peter Backes for the very
> nice testcase.
>
> This also broke xen with blktap over xfs.
Hrmph. Zach's changes in -mm magically made this go away... I was about
to submit a proper patch against -mm but it seem to be not needed.
So, now digging around to see why that is, and what exactly "fixed" things.
-Eric
prev parent reply other threads:[~2006-11-28 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 4:25 [PATCH/RFC] pass dio_complete proper offset from finished_one_bio Eric Sandeen
2006-11-26 16:18 ` Felix Blyakher
2006-11-28 14:09 ` Eric Sandeen [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=456C432E.2050601@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc@gmx.de \
--cc=xfs@oss.sgi.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 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).