From: Wei Liu <wei.liu2@citrix.com>
To: "Sébastien Chaumat" <sebastien.chaumat@qspin.be>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Please reconsider bug 26
Date: Thu, 12 May 2016 16:33:45 +0100 [thread overview]
Message-ID: <20160512153345.GN27070@citrix.com> (raw)
In-Reply-To: <CAHdho9Pw7jAnQ6Q7RqFMms9dBV9mBfMEHGsG9T5yK9GnJ9nFBQ@mail.gmail.com>
Hello
On Wed, May 11, 2016 at 04:51:41PM +0200, Sébastien Chaumat wrote:
> Hello,
>
> http://bugs.xenproject.org/xen/bug/26 is nearly 3yrs old.
>
> (bassically one can attach the same vbd rw to 2 domUs with xl without
> warning )
>
> Combined with a distribution behavior like
>
> https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1572446
>
> (a trailing domu.cfg~ backup file will be blindly used to launch twice a
> domU config with only the name changed)
>
> leads to real fun (namely filesystem corruption)
>
> Recalling early discussion here about xen philosophy, isolation accross
> domUs should be the default. Clearly xl does not provide vbd isolation by
> default.
>
> Would you mind considering implementing vbd usage detection in xl ?
>
I think xen 4.7 (which to be released soon) should fix one aspect of the
issue. Toolstack won't be able to attach same vbds twice.
And looking at the block script for Linux, it does check for "!".
Are you able to test one of the RCs (latest one RC2) for xen 4.7 to see
if it fixes the bug?
Unfortunately the fixes might be too complicated to backport.
Wei.
> Thanks,
> Sebastien
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-05-12 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 14:51 Please reconsider bug 26 Sébastien Chaumat
2016-05-12 15:33 ` Wei Liu [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=20160512153345.GN27070@citrix.com \
--to=wei.liu2@citrix.com \
--cc=sebastien.chaumat@qspin.be \
--cc=xen-devel@lists.xen.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).