1. 04 2月, 2010 2 次提交
  2. 05 10月, 2009 1 次提交
  3. 28 8月, 2009 1 次提交
  4. 12 8月, 2009 1 次提交
  5. 14 7月, 2009 1 次提交
  6. 11 5月, 2009 1 次提交
  7. 08 5月, 2009 1 次提交
  8. 16 3月, 2009 1 次提交
    • J
      Rationalize fasync return values · 60aa4924
      Jonathan Corbet 提交于
      Most fasync implementations do something like:
      
           return fasync_helper(...);
      
      But fasync_helper() will return a positive value at times - a feature used
      in at least one place.  Thus, a number of other drivers do:
      
           err = fasync_helper(...);
           if (err < 0)
                   return err;
           return 0;
      
      In the interests of consistency and more concise code, it makes sense to
      map positive return values onto zero where ->fasync() is called.
      
      Cc: Al Viro <viro@ZenIV.linux.org.uk>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      60aa4924
  9. 02 11月, 2008 1 次提交
    • A
      saner FASYNC handling on file close · 233e70f4
      Al Viro 提交于
      As it is, all instances of ->release() for files that have ->fasync()
      need to remember to evict file from fasync lists; forgetting that
      creates a hole and we actually have a bunch that *does* forget.
      
      So let's keep our lives simple - let __fput() check FASYNC in
      file->f_flags and call ->fasync() there if it's been set.  And lose that
      crap in ->release() instances - leaving it there is still valid, but we
      don't have to bother anymore.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      233e70f4
  10. 30 10月, 2008 1 次提交
  11. 01 4月, 2008 1 次提交
  12. 20 10月, 2007 1 次提交
  13. 14 10月, 2007 1 次提交
  14. 13 10月, 2007 1 次提交
  15. 30 8月, 2007 1 次提交
  16. 10 7月, 2007 1 次提交
  17. 04 6月, 2007 1 次提交
    • D
      Input: reduce raciness when input handlers disconnect · 1dfa2812
      Dmitry Torokhov 提交于
      There is a race between input handler's release() and disconnect()
      methods: when input handler disconnects it wakes up all regular
      users and then process to walk user list to wake up async. users.
      While disconnect() walks the list release() removes elements of
      the same list causing oopses.
      
      While this is not a substibute for proper locking we can reduce
      odds of getting an oops if we wake up normal readers after walking
      the list.
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      1dfa2812
  18. 09 5月, 2007 1 次提交
  19. 03 5月, 2007 1 次提交
  20. 12 4月, 2007 3 次提交
  21. 14 9月, 2006 2 次提交
  22. 26 6月, 2006 1 次提交
  23. 14 3月, 2006 1 次提交
  24. 29 10月, 2005 5 次提交
  25. 11 7月, 2005 1 次提交
  26. 21 6月, 2005 1 次提交
  27. 29 5月, 2005 1 次提交
  28. 28 5月, 2005 1 次提交
  29. 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