WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] libxl: execute command by execvp()

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] libxl: execute command by execvp()
From: Yu Zhiguo <yuzg@xxxxxxxxxxxxxx>
Date: Thu, 22 Jul 2010 10:46:49 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 21 Jul 2010 19:47:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1279700993.5872.1695.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C4424E6.4050109@xxxxxxxxxxxxxx> <4C469DB1.4090203@xxxxxxxxxxxxxx> <1279700993.5872.1695.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 3.0a1 (Windows/2008050715)
Ian Campbell wrote:
>> Yu Zhiguo wrote:
>>> execute command by execvp() so can search command in PATH.
>>>
>>  It is trivial, but can you ack this fix?
>>  Before this fix, when create guest, we must use absolute path
>> for bootloader, e.g. bootloader = "/usr/bin/pygrub".
>>  If not in absolute path now, xl create will block in:
>>
>>     pid = fork_exec_bootloader(&bootloader_fd, (char 
>> *)info->u.pv.bootloader, args);
>>  ...
>>     while (1) {
>>         fifo_fd = open(fifo, O_RDONLY); ------------> here
>>
>>  because pygrub cannot be executed so no data will be outputted into this 
>> fifo.
> 
> Hmm, perhaps we need some more error handling from fork_exec_bootloader,
> probably in addition to switching to execvp()? Perhaps a waitpid(..,..,
> WNOHANG) sometime before the fifo open to check the child hasn't gone
> away (although I'm not sure how oen makes this non-racey)?
> 

 Perhaps parent process goes to waitpid (with WNOHANG flag) but child
hasn't gone to execv("pygrub").

> Alternatively, maybe simply opening the FIFO O_NDELAY rather than using
> open+fcntl is sufficient stop stop us blocking here? I guess that would
> be safe since this is the read end of the FIFO. We would catch the
> bootloader failure (to exec or otherwise) later on in
> bootloader_interact (which either works already due to select returning
> EBADF or probably needs fixing to handle the bootloader failing
> regardless).
> 
 We can open fifo in NONBLOCK mode but I'm not sure we'll not meet
the above problem?
 What about waitpid but no WNOHANG, we can catch the exit status of child
and check it.

> Also, xend special cases the bare word "pygrub" and searches a specific
> list of likely install locations, perhaps libxl should duplicate that
> behaviour? (I think I prefer search $PATH to this but maybe consistency
> with previous behaviour trumps that?)

 I think search PATH is enough...

Yu

> 
> Ian.
> 
>> Yu
>>
>>> Signed-off-by: Yu Zhiguo <yuzg@xxxxxxxxxxxxxx>
>>>
>>> diff -r 12f0618400de -r da4c3756920e tools/libxl/libxl_exec.c
>>> --- a/tools/libxl/libxl_exec.c      Fri Jul 16 13:54:44 2010 +0100
>>> +++ b/tools/libxl/libxl_exec.c      Tue Jul 20 02:14:44 2010 +0800
>>> @@ -53,7 +53,7 @@
>>>      /* in case our caller set it to IGN.  subprocesses are entitled
>>>       * to assume they got DFL. */
>>>  
>>> -    execv(arg0, args);
>>> +    execvp(arg0, args);
>>>      _exit(-1);
>>>  }
>>>  
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>>
> 
> 
> 
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel