1. 02 2月, 2006 3 次提交
  2. 15 1月, 2006 1 次提交
  3. 11 1月, 2006 5 次提交
  4. 14 11月, 2005 1 次提交
  5. 31 10月, 2005 1 次提交
  6. 22 10月, 2005 1 次提交
    • R
      [PATCH] Call exit_itimers from do_exit, not __exit_signal · 25f407f0
      Roland McGrath 提交于
      When I originally moved exit_itimers into __exit_signal, that was the only
      place where we could reliably know it was the last thread in the group
      dying, without races.  Since then we've gotten the signal_struct.live
      counter, and do_exit can reliably do group-wide cleanup work.
      
      This patch moves the call to do_exit, where it's made without locks.  This
      avoids the deadlock issues that the old __exit_signal code's comment talks
      about, and the one that Oleg found recently with process CPU timers.
      
      [ This replaces e03d13e9, which is why
        it was just reverted. ]
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      25f407f0
  7. 08 9月, 2005 1 次提交
    • O
      [PATCH] fix send_sigqueue() vs thread exit race · e752dd6c
      Oleg Nesterov 提交于
      posix_timer_event() first checks that the thread (SIGEV_THREAD_ID case)
      does not have PF_EXITING flag, then it calls send_sigqueue() which locks
      task list.  But if the thread exits in between the kernel will oops
      (->sighand == NULL after __exit_sighand).
      
      This patch moves the PF_EXITING check into the send_sigqueue(), it must be
      done atomically under tasklist_lock.  When send_sigqueue() detects exiting
      thread it returns -1.  In that case posix_timer_event will send the signal
      to thread group.
      
      Also, this patch fixes task_struct use-after-free in posix_timer_event.
      Signed-off-by: NOleg Nesterov <oleg@tv-sign.ru>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e752dd6c
  8. 05 8月, 2005 1 次提交
  9. 29 7月, 2005 1 次提交
    • G
      [PATCH] posix timers: fix normalization problem · 78fa74a2
      George Anzinger 提交于
      (We found this (after a customer complained) and it is in the kernel.org
      kernel.  Seems that for CLOCK_MONOTONIC absolute timers and clock_nanosleep
      calls both the request time and wall_to_monotonic are subtracted prior to
      the normalize resulting in an overflow in the existing normalize test.
      This causes the result to be shifted ~4 seconds ahead instead of ~2 seconds
      back in time.)
      
      The normalize code in posix-timers.c fails when the tv_nsec member is ~1.2
      seconds negative.  This can happen on absolute timers (and
      clock_nanosleeps) requested on CLOCK_MONOTONIC (both the request time and
      wall_to_monotonic are subtracted resulting in the possibility of a number
      close to -2 seconds.)
      
      This fix uses the set_normalized_timespec() (which does not have an
      overflow problem) to fix the problem and as a side effect makes the code
      cleaner.
      Signed-off-by: NGeorge Anzinger <george@mvista.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      78fa74a2
  10. 24 6月, 2005 1 次提交
  11. 18 6月, 2005 1 次提交
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4