From: "Daniel P. Berrange" <berrange@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH]: Make Xen 3.1 IDE flush on O_DIRECT with drive caching off
Date: Tue, 26 Feb 2008 14:51:29 +0000 [thread overview]
Message-ID: <20080226145129.GD30568@redhat.com> (raw)
In-Reply-To: <47C4251A.3040000@redhat.com>
On Tue, Feb 26, 2008 at 09:41:30AM -0500, Chris Lalancette wrote:
> All,
> Long ago Xen added code to the device model to basically do an fsync()
> after every data write if the user in the guest specified that IDE write caching
> should be disabled. This works fine, except in the case where you are doing
> O_DIRECT writes inside the guest (ala dd if=/dev/zero of=/dev/hdb oflag=direct).
> This is because you can get out of ide_write_dma_cb() in the middle of the loop
> without going through the logic to sync. This simple patch makes sure that you
> always check (and sync) inside the write callback.
>
> This patch applies to xen-3.1-testing.hg; I still have to test 3.2 (and the new
> AIO code) to see if it is affected by this bug.
>
> Signed-off-by: Chris Lalancette <clalance@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
I've gone through the logic in ide_write_dma_cb() and breaking out of the
loop is the thing todo in this scenario. The new AIO code in 3.2 looks like
it suffers from a similar problem, with one of the code paths missing the
sync due to a mis-placed label / goto pair.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-02-26 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 14:41 [PATCH]: Make Xen 3.1 IDE flush on O_DIRECT with drive caching off Chris Lalancette
2008-02-26 14:51 ` Daniel P. Berrange [this message]
2008-02-28 3:23 ` Chris Lalancette
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=20080226145129.GD30568@redhat.com \
--to=berrange@redhat.com \
--cc=clalance@redhat.com \
--cc=xen-devel@lists.xensource.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.