1. 20 6月, 2009 1 次提交
  2. 11 5月, 2009 1 次提交
  3. 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
  4. 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
  5. 30 10月, 2008 1 次提交
  6. 28 10月, 2008 1 次提交
  7. 19 8月, 2008 1 次提交
  8. 09 8月, 2008 1 次提交
  9. 08 8月, 2008 1 次提交
  10. 30 6月, 2008 1 次提交
  11. 01 4月, 2008 1 次提交
  12. 31 3月, 2008 1 次提交
  13. 21 1月, 2008 1 次提交
  14. 20 10月, 2007 1 次提交
  15. 14 10月, 2007 1 次提交
  16. 13 10月, 2007 1 次提交
  17. 30 8月, 2007 1 次提交
  18. 01 8月, 2007 1 次提交
  19. 10 7月, 2007 1 次提交
  20. 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
  21. 12 5月, 2007 1 次提交
  22. 09 5月, 2007 1 次提交
  23. 03 5月, 2007 2 次提交
  24. 12 4月, 2007 3 次提交
  25. 15 3月, 2007 1 次提交
  26. 14 9月, 2006 2 次提交
  27. 19 7月, 2006 1 次提交
    • A
      Input: implement new force feedback interface · 509ca1a9
      Anssi Hannula 提交于
      Implement a new force feedback interface, in which all non-driver-specific
      operations are separated to a common module. This includes handling effect
      type validations, locking, etc.
      
      The effects are now file descriptor specific instead of the previous strange
      half-process half-fd specific behaviour. The effect memory of devices is not
      emptied if the root user opens and closes the device while another user is
      using effects. This is a minor change and most likely no force feedback
      aware programs are affected by this negatively.
      
      Otherwise the userspace interface is left unaltered.
      Signed-off-by: NAnssi Hannula <anssi.hannula@gmail.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      509ca1a9
  28. 06 7月, 2006 2 次提交
  29. 26 6月, 2006 1 次提交
  30. 23 6月, 2006 1 次提交
    • M
      [PATCH] vfs: add lock owner argument to flush operation · 75e1fcc0
      Miklos Szeredi 提交于
      Pass the POSIX lock owner ID to the flush operation.
      
      This is useful for filesystems which don't want to store any locking state
      in inode->i_flock but want to handle locking/unlocking POSIX locks
      internally.  FUSE is one such filesystem but I think it possible that some
      network filesystems would need this also.
      
      Also add a flag to indicate that a POSIX locking request was generated by
      close(), so filesystems using the above feature won't send an extra locking
      request in this case.
      Signed-off-by: NMiklos Szeredi <miklos@szeredi.hu>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      75e1fcc0
  31. 29 4月, 2006 1 次提交
  32. 14 3月, 2006 1 次提交
  33. 13 1月, 2006 1 次提交
  34. 12 1月, 2006 1 次提交
  35. 07 1月, 2006 1 次提交