1. 17 12月, 2008 1 次提交
  2. 18 11月, 2008 5 次提交
  3. 12 11月, 2008 1 次提交
  4. 06 11月, 2008 1 次提交
  5. 01 10月, 2008 2 次提交
  6. 14 9月, 2008 2 次提交
  7. 20 8月, 2008 1 次提交
  8. 31 7月, 2008 3 次提交
  9. 19 7月, 2008 1 次提交
  10. 18 7月, 2008 1 次提交
  11. 30 4月, 2008 1 次提交
  12. 26 4月, 2008 2 次提交
  13. 17 4月, 2008 1 次提交
    • R
      x86 vDSO: don't use disabled vDSO for signal trampoline · 1a3e4ca4
      Roland McGrath 提交于
      If the vDSO was not mapped, don't use it as the "restorer" for a signal
      handler.  Whether we have a pointer in mm->context.vdso depends on what
      happened at exec time, so we shouldn't check any global flags now.
      
      Background:
      
      Currently, every 32-bit exec gets the vDSO mapped even if it's disabled
      (the process just doesn't get told about it).  Because it's in fact
      always there, the bug that this patch fixes cannot happen now.  With
      the second patch, it won't be mapped at all when it's disabled, which is
      one of the things that people might really want when they disable it (so
      nothing they didn't ask for goes into their address space).
      
      The 32-bit signal handler setup when SA_RESTORER is not used refers to
      current->mm->context.vdso without regard to whether the vDSO has been
      disabled when the process was exec'd.  This patch fixes this not to use
      it when it's null, which becomes possible after the second patch. (This
      never happens in normal use, because glibc's sigaction call uses
      SA_RESTORER unless glibc detected the vDSO.)
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      1a3e4ca4
  14. 07 3月, 2008 1 次提交
  15. 30 1月, 2008 7 次提交
  16. 11 10月, 2007 1 次提交
  17. 09 5月, 2007 1 次提交
  18. 13 2月, 2007 2 次提交
  19. 07 12月, 2006 1 次提交
  20. 31 10月, 2006 1 次提交
  21. 26 9月, 2006 4 次提交