From: Michal Novotny <minovotn@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Device duplicate check fix
Date: Wed, 03 Jun 2009 10:45:08 +0200 [thread overview]
Message-ID: <4A263814.2030401@redhat.com> (raw)
In-Reply-To: <4A255EC5.3050400@eu.citrix.com>
Hi,
you don't see the need to add this check to xend since the same check is
already present in the hotplug scripts? So, is this useless and should I
do nothing about that and let it be reverted like Keir wrote he did and
do nothing about that?
Michal
Stefano Stabellini wrote:
> Sorry for the late reply, but I only now I realized that this patch
> breaks stubdoms: an exception is needed to allow a disk to be shared
> between the guest and its own stubdom.
>
> Beside I do not see the need to add this check to xend since the same
> check is already present in the hotplug scripts.
>
> Michal Novotny wrote:
>
>
>> *Hello,
>> I've checked the duplicate-check code here and I found that's checked
>> only in the context of one domain but not cross-domain. The thing is
>> that we should check tap/vbd device cross-domain not to allow another
>> guest to use the same disk image in some circumstances to prevent VM's
>> disk corruption.
>>
>> The patch included denies disk image addition under those circumstances:
>> 1. **We're adding read-only disk that's already used as write-exclusive
>> 2. **We're adding write-shared disk that's already used as write-exclusive
>> 3. **We're adding write-exclusive disk that's already used
>> 4. **We're adding read-only disk that's already used as write-shared*
>> (because of I/O caching issues etc.)
>> *
>> The vif device duplicate check remains the same it was and it's checked
>> in the context of current domain only so that behaviour has been preserved.
>>
>> Michal
>>
>> Signed-off-by: Michal Novotny <minovotn@redhat.com>
>> *
>>
>>
>
>
>
next prev parent reply other threads:[~2009-06-03 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 9:08 [PATCH] Device duplicate check fix Michal Novotny
2009-06-02 17:17 ` Stefano Stabellini
2009-06-02 22:37 ` Keir Fraser
2009-06-03 8:45 ` Michal Novotny [this message]
2009-06-03 12:08 ` 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=4A263814.2030401@redhat.com \
--to=minovotn@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.