All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/3] libxl: don't execute hotplug scripts if device is on a driver domain
Date: Fri, 3 May 2013 14:08:57 +0200	[thread overview]
Message-ID: <5183A8D9.9070109@citrix.com> (raw)
In-Reply-To: <1367581480.28742.77.camel@zakaz.uk.xensource.com>

On 03/05/13 13:44, Ian Campbell wrote:
> On Fri, 2013-05-03 at 12:23 +0100, Roger Pau Monne wrote:
>> Prevent hotplug script execution from libxl if device is on a
>> different domain.
> 
> The assumption being that the user has enabled udev in the driver
> domain?

Yes, although it doesn't have to be udev specifically, for example
something similar to xenbackendd could be used in the driver domain, but
I have only tested it with udev.

> 
> Is a log message going to be worthwhile?

There's already one log message earlier in disk_try_backend, but I guess
it won't hurt to add another one here, specifically saying that hotplug
scripts will not be executed by libxl for this specific device.

> Does this obsolete run_hotplug_scripts somewhat?

Not really, it just prevents libxl from calling hotplug scripts that
will surely fail (because the domain where the toolstack is running
doesn't have access to the device). run_hotplug_scripts tells whether
hotplug scripts will be executed by udev or libxl, so this code just
changes the behaviour when run_hotplug_scripts == 1 and backend_domid !=
TOOLSTACK_DOMID.

> 
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>> Cc: Ian Campbell <ian.campbell@citrix.com>
>> Cc: Ian Jackson <ian.jackson@citrix.com>
>> Cc: George Dunlap <george.dunlap@citrix.com>
>> ---
>>  tools/libxl/libxl_device.c |    7 +++++++
>>  1 files changed, 7 insertions(+), 0 deletions(-)
>>
>> diff --git a/tools/libxl/libxl_device.c b/tools/libxl/libxl_device.c
>> index b1fc4ef..bc86648 100644
>> --- a/tools/libxl/libxl_device.c
>> +++ b/tools/libxl/libxl_device.c
>> @@ -903,6 +903,13 @@ static void device_hotplug(libxl__egc *egc, libxl__ao_device *aodev)
>>      int hotplug;
>>      pid_t pid;
>>  
>> +    /*
>> +     * If device is attached from a driver domain don't try to execute
>> +     * hotplug scripts
>> +     */
>> +    if (aodev->dev->backend_domid != LIBXL_TOOLSTACK_DOMID)
>> +        goto out;
>> +
>>      /* Check if we have to execute hotplug scripts for this device
>>       * and return the necessary args/env vars for execution */
>>      hotplug = libxl__get_hotplug_script_info(gc, aodev->dev, &args, &env,
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-05-03 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 11:23 [PATCH 0/3] libxl: allow usage of storage driver domains Roger Pau Monne
2013-05-03 11:23 ` [PATCH 1/3] libxl: correctly parse storage devices on " Roger Pau Monne
2013-05-03 11:42   ` Ian Campbell
2013-05-03 11:48   ` George Dunlap
2013-05-03 15:21     ` George Dunlap
2013-05-07 17:28   ` Ian Jackson
2013-05-08  8:47     ` George Dunlap
2013-05-08 11:33       ` Ian Campbell
2013-05-03 11:23 ` [PATCH 2/3] libxl: don't execute hotplug scripts if device is on a driver domain Roger Pau Monne
2013-05-03 11:44   ` Ian Campbell
2013-05-03 12:08     ` Roger Pau Monné [this message]
2013-05-03 12:38   ` Ian Campbell
2013-05-03 11:23 ` [PATCH 3/3] libxl: don't write physical-device node for driver domain disks Roger Pau Monne
2013-05-03 11:45   ` Ian Campbell
2013-05-03 12:09     ` Roger Pau Monné
2013-05-03 12:38   ` Ian Campbell
2013-05-07 15:47 ` [PATCH 0/3] libxl: allow usage of storage driver domains Roger Pau Monné

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=5183A8D9.9070109@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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 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.