Ubuntu
lxc package

potential race in commands.c / lxc-info

Bug #1124526 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

There have been reports that two racing lxc-infos can result in one of the lxc-infos being hung. I've tried to reproduce with the script below - so far with no success, but that doesn't mean the race isn't real.

#!/bin/sh

if [ $(id -u) -ne 0 ]; then
 echo "run as root"
 exit 1
fi

if [ "x$1" = "x" ]; then
 echo "give name of container to play with as arg 1"
 exit 1
fi

(lxc-start -n $1 -d; lxc-info -n $1) &
(lxc-stop -n $1; lxc-info -n $1)

Serge Hallyn (serge-hallyn)
Changed in lxc (Ubuntu):
importance: Undecided → Low
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

This is probably related to bug 1134923 - i suspect both are due to bugs in the monitor code.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I believe this is fixed in upstream git.

Changed in lxc (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc - 1.0.0~alpha1-0ubuntu2

---------------
lxc (1.0.0~alpha1-0ubuntu2) saucy; urgency=low

  * Add allow-stderr to autopkgtst restrictions as the Ubuntu template
    uses policy-rc.d to disable some daemons and that causes a message to
    be printed on stderr when the service tries to start.
 -- Stephane Graber <email address hidden> Thu, 12 Sep 2013 13:57:17 -0400

Changed in lxc (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.