1. 15 Mar, 2018 1 commit
    • fix handler use-after-free · a3b4f3d6
      Tycho Andersen authored
      The problem here is that __lxc_start frees the handler, so any use
      afterwards is invalid. Since we don't have access to the actual struct
      lxc_container object in __lxc_start, let's pass a pointer to error_num in
      so it can be returned.
      
      Unfortunately, I'm a little too paranoid to change the return type of
      lxc_start, since it returns failure if some of the cleanup fails, which
      may be useful in some cases. So let's keep this out of band.
      
      Closes #2218
      Closes #2219
      Reported-by: 's avatarFelix Abecassis <fabecassis@nvidia.com>
      Signed-off-by: 's avatarTycho Andersen <tycho@tycho.ws>
  2. 13 Mar, 2018 4 commits
  3. 12 Mar, 2018 2 commits
  4. 09 Mar, 2018 2 commits
  5. 03 Mar, 2018 2 commits
  6. 02 Mar, 2018 7 commits
  7. 01 Mar, 2018 7 commits
  8. 28 Feb, 2018 15 commits