1. 06 Mar, 2017 1 commit
    • seccomp: set SCMP_FLTATR_ATL_TSKIP if available · 127c5293
      Serge Hallyn authored
      Newer libseccomp has a flag called SCMP_FLTATR_ATL_TSKIP which
      allows syscall '-1' (nop) to be executed.  Without that flag,
      debuggers cannot skip system calls inside containers.  For reference,
      see the seccomp(2) manpage, which says:
      
      	The tracer can skip the system call by changing the system call  number  to  -1.
      
      and see the seccomp issue #80
      Signed-off-by: 's avatarSerge Hallyn <serge@hallyn.com>
  2. 03 Mar, 2017 1 commit
  3. 02 Mar, 2017 1 commit
  4. 27 Feb, 2017 2 commits
  5. 26 Feb, 2017 2 commits
  6. 25 Feb, 2017 1 commit
  7. 23 Feb, 2017 4 commits
  8. 22 Feb, 2017 1 commit
  9. 19 Feb, 2017 2 commits
  10. 18 Feb, 2017 6 commits
  11. 17 Feb, 2017 1 commit
  12. 16 Feb, 2017 1 commit
  13. 15 Feb, 2017 2 commits
  14. 12 Feb, 2017 3 commits
    • Merge pull request #1430 from ffontaine/master · 1f14c2ea
      Christian Brauner authored
      Add HAVE_LIBCAP
    • Add HAVE_LIBCAP · e37dda71
      Fabrice Fontaine authored
      Currently it is impossible to build lxc with --disable-capabilities if
      the user has libcap-dev installed on his system as:
       - calls to cap_xxx functions are not protected by HAVE_LIBCAP defines.
       The whole file is only protected by HAVE_SYS_CAPABILITY_H.
       - AC_CHECK_LIB default action-if-found is overriden by [true] so
       HAVE_LIBCAP is never written to config.h
      
      This patch replaces all HAVE_SYS_CAPABILITY_H checks by HAVE_LIBCAP
      checks (fix #1361)
      Signed-off-by: 's avatarFabrice Fontaine <fontaine.fabrice@gmail.com>
    • seccomp: allow x32 guests on amd64 hosts. · 11de80d6
      Adam Borowski authored
      Without this patch, x32 guests (and no others) worked "natively" with x32
      host lxc, but not on regular amd64 hosts.  That was especially problematic
      as a number of ioctls such as those needed by netfilter don't work in such
      scenarios, thus you want to run amd64 on the host.
      
      With the patch, you can use all three ABIs: i386 x32 amd64 on amd64 hosts.
      
      Despite x32 being little used, there's no reason to deny it by default:
      the admin needs to compile their own kernel with CONFIG_X86_X32=y or (on
      Debian) boot with syscall.x32=y.  If they've done so, it is a reasonable
      assumption they want x32 guests.
      Signed-off-by: 's avatarAdam Borowski <kilobyte@angband.pl>
  15. 08 Feb, 2017 4 commits
    • Merge pull request #1424 from brauner/2017-02-08/thomasDOTjaroschATintra2netDOTcom_pty_sigttou · 3a5cb1af
      Stéphane Graber authored
      lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals
    • Merge pull request #1425 from cebe/patch-1 · b93fbd24
      Stéphane Graber authored
      Make lxc-net return non-zero on failure
    • Make lxc-net return non-zero on failure · 4f4e7141
      Carsten Brandt authored
      I found that even though the service lxc-net failed to start because I made some wrong configuration
      settings the command exists zero.
      So systemd reports the status of the service as good even though it failed:
      
          # service lxc-net status
          ● lxc-net.service - LXC network bridge setup
             Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled)
             Active: active (exited) since Wed 2017-02-08 08:17:32 EST; 21min ago
            Process: 529 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start (code=exited, status=0/SUCCESS)
           Main PID: 529 (code=exited, status=0/SUCCESS)
             CGroup: /system.slice/lxc-net.service
      
          Feb 08 08:17:30 dvm2 systemd[1]: Starting LXC network bridge setup...
          Feb 08 08:17:32 dvm2 lxc-net[529]: dnsmasq: failed to create listening socket for 10.2.2.1: Address already in use
          Feb 08 08:17:32 dvm2 lxc-net[529]: Failed to setup lxc-net.
          Feb 08 08:17:32 dvm2 systemd[1]: Started LXC network bridge setup.
      
      Adding `exit 1` here makes it exit non-zero to make systemd recognize the failure.
      Signed-off-by: 's avatarCarsten Brandt <mail@cebe.cc>
    • lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals · 4dc96430
      Thomas Jarosch authored
      Prevent an endless loop while executing lxc-attach in the background:
      
      The kernel might fire SIGTTOU while an ioctl() in tcsetattr()
      is executed. When the ioctl() is resumed and retries,
      the signal handler interrupts it again.
      
      We can't configure the TTY to stop sending
      the signals in the first place since that
      is a modification/write to the TTY already.
      
      Still we clear the TOSTOP flag to prevent further signals.
      
      Command to reproduce the hang:
      ----------------------------
      cat > lxc_hang.sh << EOF
      /usr/bin/timeout 5s /usr/bin/lxc-attach -n SOMECONTAINER -- /bin/true
      EOF
      sh lxc_hang.sh    # hangs
      ----------------------------
      Signed-off-by: 's avatarThomas Jarosch <thomas.jarosch@intra2net.com>
  16. 07 Feb, 2017 2 commits
  17. 06 Feb, 2017 3 commits
  18. 02 Feb, 2017 3 commits