[lxc-devel] [GIT] lxc branch, master, updated. d1c383f39064969b647fd632f8e6614b49fd6cf2

[Daniel Lezcano]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".

The branch, master has been updated
       via  d1c383f39064969b647fd632f8e6614b49fd6cf2 (commit)
       via  371828c4a0a23b61d57889b7deb11390b6ff0f3e (commit)
       via  ba31511e05aa098a22552b1c8da39e80ae4a090c (commit)
      from  ebb9ec72ce494cbee4bb445604d6527fbaefde5b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d1c383f39064969b647fd632f8e6614b49fd6cf2
Author: Daniel Lezcano <dlezcano at fr.ibm.com>
Date:   Mon Jul 12 15:13:18 2010 +0200

    fix compilation warning
    
    Add missing include.
    
    Signed-off-by: Daniel Lezcano <dlezcano at fr.ibm.com>

commit 371828c4a0a23b61d57889b7deb11390b6ff0f3e
Author: Sukadev Bhattiprolu <sukadev at linux.vnet.ibm.com>
Date:   Mon Jul 12 15:13:18 2010 +0200

    Must unfreeze while stopping container
    
    As pointed out by Dan Smith, when a container is being stopped, it must
    also be unfrozen after posting the SIGKILL. Otherwise if the container
    is frozen when the SIGKILL is posted, the SIGKILL will remain pending
    and the lxc-stop command will block until lxc-unfreeze is explicitly
    called).
    
    (lxc-stop waits for the container to exit and close the socket but since
    the container is frozen, lxc-stop will block).
    
    Signed-off-by: Sukadev Bhattiprolu <sukadev at linux.vnet.ibm.com>
    Acked-by: Matt Helsley <matthltc at us.ibm.com>
    Acked-by: Dan Smith <danms at us.ibm.com>
    Signed-off-by: Daniel Lezcano <dlezcano at fr.ibm.com>

commit ba31511e05aa098a22552b1c8da39e80ae4a090c
Author: Sukadev Bhattiprolu <sukadev at linux.vnet.ibm.com>
Date:   Mon Jul 12 15:13:18 2010 +0200

    Ensure frezer state has changed
    
    A write to the freezer.state file does not gurantee that the state has
    changed. To ensure that the freezer state is either FROZEN or THAWED,
    read the freezer state and if it has not changed, repeat the write.
    
    Changelog[v2]:
    	- Minor reorg of code
    	- Comments from Daniel Lezcano:
    		- lseek() before each read/write of freezer.state
    		- Have lxc_freeze_unfreeze() return -1 on error
    
    Signed-off-by: Sukadev Bhattiprolu <sukadev at linux.vnet.ibm.com>
    Signed-off-by: Daniel Lezcano <dlezcano at fr.ibm.com>

-----------------------------------------------------------------------

Summary of changes:
 src/lxc/freezer.c |   50 +++++++++++++++++++++++++++++++++++++++++++-------
 src/lxc/stop.c    |   11 +++++++++--
 2 files changed, 52 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
lxc