Re: [lxc-devel] [PATCH 1/1] locking: update per Dwight's comment

2013-05-24 Thread Serge Hallyn
Quoting Dwight Engen (dwight.en...@oracle.com): > Looks good to me, much cleaner in lxccontainer.c, nice! Minor question: > can lxclock() and lxcunlock() be made static now? Oh, heh, except src/test/locktests.c is still testing lxclock by hand :) So it'll have to be updated to use the wrapper fu

Re: [lxc-devel] [PATCH 1/1] locking: update per Dwight's comment

2013-05-24 Thread Serge Hallyn
Quoting Dwight Engen (dwight.en...@oracle.com): > On Fri, 24 May 2013 16:09:59 -0500 > Serge Hallyn wrote: > > > ( These are pushed to github.com/hallyn/lxc branch > > lxclock-flock.rebase ) > > > > Create three pairs of functions: > > int process_lock(void); > > void process_unlock(void

Re: [lxc-devel] [PATCH 1/1] locking: update per Dwight's comment

2013-05-24 Thread Dwight Engen
On Fri, 24 May 2013 16:09:59 -0500 Serge Hallyn wrote: > ( These are pushed to github.com/hallyn/lxc branch > lxclock-flock.rebase ) > > Create three pairs of functions: > int process_lock(void); > void process_unlock(void); > int container_mem_lock(struct lxc_container *c) >

[lxc-devel] [PATCH 1/1] locking: update per Dwight's comment

2013-05-24 Thread Serge Hallyn
( These are pushed to github.com/hallyn/lxc branch lxclock-flock.rebase ) Create three pairs of functions: int process_lock(void); void process_unlock(void); int container_mem_lock(struct lxc_container *c) void container_mem_unlock(struct lxc_container *c) i