1. 20 11月, 2008 2 次提交
  2. 14 11月, 2008 1 次提交
    • D
      USB: gadget: cdc-acm deadlock fix · e50ae572
      David Brownell 提交于
      This fixes a deadlock appearing with some USB peripheral drivers
      when running CDC ACM gadget code.
      
      The newish (2.6.27) CDC ACM event notification mechanism sends
      messages (IN to the host) which are short enough to fit in most
      FIFOs.  That means that with some peripheral controller drivers
      (evidently not the ones used to verify the notification code!!)
      the completion callback can be issued before queue() returns.
      
      The deadlock would come because the completion callback and the
      event-issuing code shared a spinlock.  Fix is trivial:  drop
      that lock while queueing the message.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: stable <stable@kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      e50ae572
  3. 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
  4. 23 10月, 2008 3 次提交
  5. 18 10月, 2008 27 次提交
  6. 17 10月, 2008 6 次提交