1. 25 Dec, 2018 3 commits
  2. 24 Dec, 2018 1 commit
  3. 22 Dec, 2018 1 commit
  4. 21 Dec, 2018 1 commit
  5. 20 Dec, 2018 1 commit
  6. 17 Dec, 2018 1 commit
  7. 22 Nov, 2018 2 commits
  8. 21 Nov, 2018 2 commits
  9. 18 Nov, 2018 4 commits
  10. 16 Nov, 2018 1 commit
  11. 15 Nov, 2018 1 commit
  12. 13 Nov, 2018 1 commit
  13. 11 Nov, 2018 4 commits
  14. 08 Nov, 2018 2 commits
  15. 06 Nov, 2018 1 commit
  16. 30 Oct, 2018 1 commit
  17. 28 Oct, 2018 1 commit
    • Aleksa Sarai's avatar
      codegen: stack: allow for inter-tid stack aggregation · c4a5de20
      Aleksa Sarai authored
      User-space stacks are quite special in regards to aggregation (and
      comparison) between processes. To a first approximation, each pid has a
      different memory mapping and thus pointers should not be compared or
      aggregated between pids[*]. With ASLR this becomes even more fun, and
      thus it is necessary to do usym()-style packing of the stackid for
      ustack (since bpf_get_stackid will give you a hash of the pointers --
      even in the ustack case).
      
      However, the kernel address space is the same regardless of current->pid
      -- and in many cases you want to aggregate between different processes
      (and if not, you can always do the packing yourself with @[tid,stack]).
      
      So, we only apply the packing when dealing with ustack. sym() already
      does the right thing.
      
      [*] This is more than slightly untrue -- really this depends on
          current->mm and ideally we would aggregate ustack on current->mm.
          Unfortunately this is not a luxury we have at the moment.
      Signed-off-by: default avatarAleksa Sarai <cyphar@cyphar.com>
      c4a5de20
  18. 27 Oct, 2018 2 commits
  19. 26 Oct, 2018 2 commits
  20. 25 Oct, 2018 1 commit
  21. 24 Oct, 2018 2 commits
  22. 22 Oct, 2018 2 commits
  23. 21 Oct, 2018 2 commits
  24. 20 Oct, 2018 1 commit