From: George Dunlap <george.dunlap@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: introduce an option for disabling the non-O_DIRECT workaround
Date: Tue, 26 Nov 2013 17:56:54 +0000 [thread overview]
Message-ID: <5294E0E6.1070305@eu.citrix.com> (raw)
In-Reply-To: <20131126174617.GM2959@phenom.dumpdata.com>
On 11/26/2013 05:46 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 26, 2013 at 11:42:31AM +0000, Ian Jackson wrote:
>> From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>
>> Document and implement a new option that permits disk backends which
>> would otherwise have to avoid O_DIRECT (because of the network memory
>> lifetime bug) to use it anyway. This is:
>
> I thought this was fixed in the Linux kernel with:
>
> commit cd9151e26d31048b2b5e00fd02e110e07d2200c9
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date: Sun Aug 4 15:39:40 2013 +0100
>
> xen/balloon: set a mapping for ballooned out pages
>
> Currently ballooned out pages are mapped to 0 and have INVALID_P2M_ENTRY
> in the p2m. These ballooned out pages are used to map foreign grants
> by gntdev and blkback (see alloc_xenballooned_pages).
>
> Allocate a page per cpu and map all the ballooned out pages to the
> corresponding mfn. Set the p2m accordingly. This way reading from a
> ballooned out page won't cause a kernel crash (see
> http://lists.xen.org/archives/html/xen-devel/2012-12/msg01154.html).
>
>
> ?
Not everyone builds her own kernel from the latest release; until we can
be relatively sure that this fix has hit distros (including older
LTS-style ones), we have to deal with the fact that the O_DIRECT bug may
be present. The purpose of this flag is to enable you to turn it on
when you know it's safe -- for instance, if you're running a kernel with
this changeset.
It is worth asking the question now though: Given that this has been
checked in, would it make sense to switch the polarity of this --
default to O_DIRECT on and have a flag to allow people to switch it off?
If not now, maybe for 4.5? And in that case, maybe we should change
the argument to be tristate: default, true, or false (i.e., true means I
know it's safe, false means I know it's unsafe, default means I haven't
specified either way)?
-George
next prev parent reply other threads:[~2013-11-26 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 11:42 [PATCH RESEND 0/1] libxl: introduce an option for disabling the non-O_DIRECT Ian Jackson
2013-11-26 11:42 ` [PATCH] libxl: introduce an option for disabling the non-O_DIRECT workaround Ian Jackson
2013-11-26 17:46 ` Konrad Rzeszutek Wilk
2013-11-26 17:56 ` George Dunlap [this message]
2013-11-26 18:18 ` Konrad Rzeszutek Wilk
2013-11-28 11:38 ` [PATCH] libxl: introduce an option for disabling the non-O_DIRECT workaround [and 1 more messages] Ian Jackson
2013-11-28 11:46 ` George Dunlap
2013-11-28 17:32 ` Ian Jackson
2014-04-02 12:26 ` Felipe Franciosi
2014-04-03 10:12 ` Stefano Stabellini
2014-04-03 10:51 ` Felipe Franciosi
2014-04-03 11:41 ` Ian Campbell
2014-04-03 12:53 ` Stefano Stabellini
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=5294E0E6.1070305@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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 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.