All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Tagging Xen 4.0.0 first release candidate / pygrub dom0 caching bug
Date: Thu, 21 Jan 2010 19:37:27 +0000	[thread overview]
Message-ID: <1264102647.21707.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1264101384.12544.3765.camel@agari.van.xensource.com>

On Thu, 2010-01-21 at 19:16 +0000, Daniel Stodden wrote: 
> On Thu, 2010-01-21 at 13:44 -0500, Daniel Stodden wrote:
> > On Thu, 2010-01-21 at 07:28 -0500, Pasi Kärkkäinen wrote:
> > > On Wed, Jan 06, 2010 at 03:50:05PM +0200, Pasi Kärkkäinen wrote:
> > > > On Tue, Jan 05, 2010 at 06:42:05AM +0000, Keir Fraser wrote:
> > > > > I plan to tag -rc1 later this week. If you have any outstanding patches,
> > > > > please send them to the list now.
> > > > > 
> > > > 
> > > > Hmm.. I just remembered this pygrub bug:
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=466681
> > > > 
> > > > pygrub doesn't use O_DIRECT so sometimes it gets old information
> > > > from dom0 kernel cache - and fails to use the updated domU grub.conf.
> > > > 
> > > > Redhat seems to have patches available for testing.. not for
> > > > xen-unstable though.
> > > > 
> > > > I've personally hit this bug many times.
> > > > 
> > > 
> > > It seems Redhat guys have a fix available.. they fixed the problem by 
> > > patching dom0 kernel blkback.
> > > 
> > > More details about the fix here:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=466681
> > > 
> > > Should this be applied to 2.6.18-xen and pv_ops dom0 kernels aswell? 
> > 
> > Only to 2.6.18. 
> > 
> > It's obsolete after 2.6.27.
> > O_DIRECT gained page cache invalidation in the meantime.
> 
> Aiiee, sorry. I guess this one only applies to tapdisks. The page cache
> invalidation only covers the filemap. That obviously won't fix blkback
> bios on raw devices.
> 
> Ian Campbell recently noted he came across a different fix, which adds
> direct-io to e2fsprogs.

I noted the thread because the root problem seemed interesting and
worthy of investigation, but I should have made it clear that I didn't
think messing with direct-io in e2fsprogs was the correct solution. I
think the majority of the participants in the thread thought that too.
The biggest problem is that it only solves the issue in the one specific
case of things which use e2fsprogs and not in general, we can't go round
adding O_DIRECT to everything which might be used to access these disks.

Ian.

> 
> http://www.spinics.net/lists/linux-ext4/msg16992.html
> 
> Any opinions on the tradeoff?
> 
> Daniel
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-01-21 19:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  6:42 Tagging Xen 4.0.0 first release candidate Keir Fraser
2010-01-05  8:56 ` Jan Beulich
2010-01-05  9:06   ` Keir Fraser
2010-01-05 16:00     ` Alex Williamson
2010-01-05 16:06       ` Keir Fraser
2010-01-19 13:57         ` Tagging Xen 4.0.0 first release candidate, 44-bit address space support Pasi Kärkkäinen
2010-01-19 14:02           ` Keir Fraser
2010-01-19 14:22             ` Pasi Kärkkäinen
2010-01-06 13:50 ` Tagging Xen 4.0.0 first release candidate / pygrub dom0 caching bug Pasi Kärkkäinen
2010-01-21 12:28   ` Pasi Kärkkäinen
2010-01-21 15:39     ` Jan Beulich
2010-01-21 18:44     ` Daniel Stodden
2010-01-21 19:16       ` Daniel Stodden
2010-01-21 19:37         ` Ian Campbell [this message]
2010-01-21 21:01           ` Pasi Kärkkäinen
2010-01-21 21:53             ` Daniel Stodden
2010-01-27  9:27               ` Pasi Kärkkäinen
2010-01-28 19:34                 ` Daniel Stodden
2010-01-06 15:00 ` Tagging Xen 4.0.0 first release candidate Christian Tramnitz
2010-01-06 21:42   ` Ian Pratt
2010-01-06 21:52     ` Pasi Kärkkäinen
2010-01-07 11:51   ` Pasi Kärkkäinen

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=1264102647.21707.2.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=daniel.stodden@citrix.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.