1. 23 3月, 2007 1 次提交
  2. 16 3月, 2007 1 次提交
    • S
      [CIFS] Do not negotiate new POSIX_PATH_OPERATIONS_CAP yet · 38e2aff6
      Steve French 提交于
      Samba server now expects that clients which send the new
      POSIX_PATH_OPERATIONS_CAP send all opens with this new
      SMB - and expects that clients that could send the new
      posix open/create but don't as indicating that they really
      want Windows semantics on that handle (which allows Samba
      to support clients which want to support both types of
      behaviors on different handles on the same mount)
      
      We will put this capability back in the SetFSInfo
      negotiation with servers like Samba when the
      new POSIXCreate (create/open/mkdir) code is finished.
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      38e2aff6
  3. 10 3月, 2007 1 次提交
  4. 08 3月, 2007 12 次提交
  5. 07 3月, 2007 3 次提交
    • H
      [PATCH] suspend regression: sysfs deadlock · 266d4f40
      Hugh Dickins 提交于
      Suspend deadlocks when trying to unregister /sys/block/sr0.
      
      This comes from Oliver's commit 94bebf4d
      "Driver core: fix race in sysfs between sysfs_remove_file() and
      read()/write()".
      
      sysfs_write_file downs buffer->sem while calling flush_write_buffer, and
      flushing that particular write buffer entails downing buffer->sem in
      orphan_all_buffers, resulting in the obvious self-deadlock.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      266d4f40
    • D
      [PATCH] fs: nobh_truncate_page() fix · 57bf63d6
      Dave Kleikamp 提交于
      This fixes a regression caused by 22c8ca78.
      
      nobh_prepare_write() no longer marks the page uptodate, so
      nobh_truncate_page() needs to do it.
      Signed-off-by: NDave Kleikamp <shaggy@linux.vnet.ibm.com>
      Cc: Nick Piggin <nickpiggin@yahoo.com.au>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      57bf63d6
    • M
      [PATCH] Fix 2.6.21 rfcomm lockups · 0de1517e
      Mark Lord 提交于
      Any attempt to open/use a bluetooth rfcomm device locks up
      scheduling completely on my machine.
      
      Interrupts (ping, alt-sysrq) seem to be alive, but nothing else.
      
      This was working fine in 2.6.20, broken now in 2.6.21-rc2-git*
      
      Reverting this change (below) fixes it:
      
      | author    Marcel Holtmann <marcel@holtmann.org>
      |      Sat, 17 Feb 2007 22:58:57 +0000 (23:58 +0100)
      | committer    David S. Miller <davem@sunset.davemloft.net>
      |      Mon, 26 Feb 2007 19:42:41 +0000 (11:42 -0800)
      | commit    c1a33136
      | tree    337a876f727061362b6a169f8759849c105b8f7a    tree | snapshot
      | parent    f5ffd462    commit | diff
      | | [Bluetooth] Make use of device_move() for RFCOMM TTY devices
      | | In the case of bound RFCOMM TTY devices the parent is not available
      | before its usage. So when opening a RFCOMM TTY device, move it to
      | the corresponding ACL device as a child. When closing the device,
      | move it back to the virtual device tree.
      | Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
      
      The simplest fix for this bug is to prevent sysfs_move_dir()
      from self-deadlocking when (old_parent == new_parent).
      
      This patch prevents total system lockup when using rfcomm devices.
      Signed-off-by: NMark Lord <mlord@pobox.com>
      Acked-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0de1517e
  6. 06 3月, 2007 2 次提交
  7. 05 3月, 2007 4 次提交
  8. 02 3月, 2007 5 次提交
  9. 01 3月, 2007 1 次提交
  10. 27 2月, 2007 5 次提交
  11. 24 2月, 2007 2 次提交
  12. 21 2月, 2007 3 次提交
新手
引导
客服 返回
顶部