- 13 Dec, 2017 3 commits
-
-
Stéphane Graber authored
start: do not unconditionally dup std{in,out,err} -
Christian Brauner authored
confile: add lxc.proc.* to set proc filesystem
-
Yifeng Tan authored
Signed-off-by:Yifeng Tan <tanyifeng1@huawei.com>
-
- 12 Dec, 2017 2 commits
-
-
Christian Brauner authored
Starting with commit commit c5b93afb Author: Li Feng <lifeng68@huawei.com> Date: Mon Jul 10 17:19:52 2017 +0800 start: dup std{in,out,err} to pty slave In the case the container has a console with a valid slave pty file descriptor we duplicate std{in,out,err} to the slave file descriptor so console logging works correctly. When the container does not have a valid slave pty file descriptor for its console and is started daemonized we should dup to /dev/null. Closes #1646. Signed-off-by:Li Feng <lifeng68@huawei.com> Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com> we made std{err,in,out} a duplicate of the slave file descriptor of the console if it existed. This meant we also duplicated all of them when we executed application containers in the foreground even if some std{err,in,out} file descriptor did not refer to a {p,t}ty. This blocked use cases such as: echo foo | lxc-execute -n -- cat which are very valid and common with application containers but less common with system containers where we don't have to care about this. So my suggestion is to unconditionally duplicate std{err,in,out} to the console file descriptor if we are either running daemonized - this ensures that daemonized application containers with a single bash shell keep on working - or when we are not running an application container. In other cases we only duplicate those file descriptors that actually refer to a {p,t}ty. This logic is similar to what we do for lxc-attach already. Refers to #1690. Closes #2028. Reported-by:
Felix Abecassis <fabecassis@nvidia.com> Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
overlay: fix out-of-bounds copy
-
- 11 Dec, 2017 10 commits
-
-
Jonathan Calmels authored
Signed-off-by:Jonathan Calmels <jcalmels@nvidia.com>
-
Serge Hallyn authored
start: intelligently use clone() on ns sharing
-
Christian Brauner authored
This also ensures that the new more efficient clone() way of sharing namespaces is tested. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
When I first solved this problem I went for a fork() + setns() + clone() model. This works fine but has unnecessary overhead for a couple of reasons: - doing a full fork() including copying file descriptor table and virtual memory - using pipes to retrieve the pid of the second child (the actual container process) This can all be avoided by being a little smart in how we employ the clone() syscall: - using CLONE_VM will let us get rid of using pipes since we can simply write to the handler because we share the memory with our parent - using CLONE_VFORK will also let us get rid of using pipes since the execution of the parent is suspended until the child returns - using CLONE_VM will not cause virtual memory to be copied - using CLONE_FILES will not cause the file descriptor table to be copied Note that the intermediate clone() is used with CLONE_VM. Some glibc versions used to reset the pid/tid to -1 when CLONE_VM was used without CLONE_THREAD. But since the memory between parent and child is shared on CLONE_VM this would invalidate the getpid() cache that glibc used to maintain and so getpid() in the child would return the parent's pid. This is all fixed in newer glibc versions where the getpid() cache is removed and the pid/tid is not reset anymore. However, if for whatever reason you - dear commiter - somehow need to get the pid of the dummy intermediate process for do_share_ns() you need to call syscall(__NR_getpid) directly. The next lxc_clone() call does not employ CLONE_VM and will be fine. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
confile: add lxc.sysctl config
-
LiFeng authored
Signed-off-by:LiFeng <lifeng68@huawei.com>
-
Stéphane Graber authored
legacy confile: fix legacy network parser
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
This fixes a bug introduced by: commit 94f0035b Author: Christian Brauner <christian.brauner@ubuntu.com> Date: Thu Dec 7 15:07:26 2017 +0100 coverity: #1425924 remove logically dead condition Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com> Coverity's bug analysis is correct but my fix wasn't. This commit fixes a bunch of other bugs I just spotted as well. This unblocks #2009. Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com>
-
- 09 Dec, 2017 7 commits
-
-
Stéphane Graber authored
Signed-off-by:Stéphane Graber <stgraber@ubuntu.com>
-
Serge Hallyn authored
lxc-oci misc improvements
-
Felix Abecassis authored
Signed-off-by:Felix Abecassis <fabecassis@nvidia.com>
-
Serge Hallyn authored
lxc: Distinguish pthread_mutex_unlock error messages
-
Serge Hallyn authored
bugfixes
-
Felix Abecassis authored
Signed-off-by:Felix Abecassis <fabecassis@nvidia.com>
-
Felix Abecassis authored
Signed-off-by:Felix Abecassis <fabecassis@nvidia.com>
-
- 08 Dec, 2017 1 commit
-
-
Marcos Paulo de Souza authored
The same message exists in lxclock.c and cgmanager.c, so print the filename along with the message. Before this patch: lxc-destroy -n u1 pthread_mutex_unlock returned:1 Operation not permitted After this patch: xc-destroy -n u1 lxclock.c: pthread_mutex_unlock returned:1 Operation not permitted Signed-off-by:Marcos Paulo de Souza <marcos.souza.org@gmail.com>
-
- 07 Dec, 2017 11 commits
-
-
Serge Hallyn authored
coverity: bugfixes
-
Christian Brauner authored
check return value of getifaddrs() Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
do not call close on bad file descriptor Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
silence complaint about unchecked return value from library function Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
free allocated memory Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
free allocated memory Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
free allocated memory Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
avoid NULL-pointer dereference Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
remove logically dead condition Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Avoid NULL-pointer dereference. Apparently monitor.{c,h} calls lxc_check_inherited() with NULL passed for the config. This isn't really a big issue since monitor.{c,h} is effectively dead for all liblxc versions that have the state client patch. Also, the patch that introduces the relevant lines into lxc_check_inherited() is only in master and yet unreleased. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
free allocated memory Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
- 06 Dec, 2017 6 commits
-
-
Stéphane Graber authored
coverity: bugfixes
-
Serge Hallyn authored
commands: improve and simplify locking + lxccontainer: add reboot2() API extension
-
Christian Brauner authored
remove logically dead code Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
fix error condition check Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
free allocated memory Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
check snprintf() return value Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-