From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Christian Limpach <Christian.Limpach@xensource.com>,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: feature request - prevent user stupidity (eg mine)
Date: Fri, 29 Jun 2007 03:47:33 +0100 [thread overview]
Message-ID: <200706290347.34026.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <17C7B9F697482Bkanno.masaki@jp.fujitsu.com>
> >The nice thing about the hotplug scripts is that they Just Work for
> >dynamically adding devices. Unless I've misread Kan's code, it won't
> > catch a user accidentally adding a duplicate blkdev to a running domain,
> > which is a shame.
>
> Could you teach me a blkdev definition or a adding blkdev operation that
> my code cannot catch that you think of? I'd like to test them by my code.
I was thinking your code didn't get run at block-attach, but later on I
started to think maybe it was :-) Is it? ;-)
> >We should try to figure out if this can be added reliably to the blkdev
> >hotplug scripts. If not, maybe we should put all the checking into Xend,
> >with hooks to validate added devices.
>
> I'd like to check a duplicate blkdev for both xm new command and xm create
> command, so that I added the checking into xend(XendConfig.py).
> If the duplicate blkdev is notified of by xm start command, I think that
> it is late.
Ah, I hadn't thought about xm new. Well, in that case it sounds fairly
reasonable to add to Xend, and your code looked OK to me. Given that, I'd
have no objections to your patch going in. Might save me from PBKAC (Problem
Between Keyboard And Chair) one day :-)
Cheers,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
next prev parent reply other threads:[~2007-06-29 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 14:10 feature request - prevent user stupidity (eg mine) James Harper
2007-06-28 2:52 ` Ian Pratt
2007-06-28 4:04 ` Masaki Kanno
2007-06-29 0:05 ` Mark Williamson
2007-06-29 1:17 ` Daniel P. Berrange
2007-06-29 1:36 ` Mark Williamson
2007-06-29 2:38 ` Masaki Kanno
2007-06-29 2:47 ` Mark Williamson [this message]
2007-06-29 8:25 ` Masaki Kanno
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=200706290347.34026.mark.williamson@cl.cam.ac.uk \
--to=mark.williamson@cl.cam.ac.uk \
--cc=Christian.Limpach@xensource.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=james.harper@bendigoit.com.au \
--cc=kanno.masaki@jp.fujitsu.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.