1. 16 6月, 2009 1 次提交
  2. 24 5月, 2009 2 次提交
  3. 27 4月, 2009 1 次提交
  4. 01 4月, 2009 1 次提交
  5. 13 3月, 2009 3 次提交
  6. 30 12月, 2008 1 次提交
  7. 25 12月, 2008 1 次提交
  8. 06 11月, 2008 1 次提交
  9. 04 10月, 2008 4 次提交
  10. 29 8月, 2008 1 次提交
  11. 12 7月, 2008 2 次提交
  12. 19 4月, 2008 1 次提交
  13. 08 4月, 2008 3 次提交
  14. 25 1月, 2008 1 次提交
  15. 12 1月, 2008 1 次提交
  16. 13 10月, 2007 1 次提交
  17. 12 10月, 2007 1 次提交
  18. 16 5月, 2007 1 次提交
    • M
      [SCSI] zfcp: IO stall after deleting and path checker changes after reenabling zfcp devices · 9f28745a
      Michael Loehr 提交于
      IO stall after deleting and path checker changes after reenabling zfcp device
      
      Setting one zfcp device offline using chccwdev in a multipath
      environment and waiting will lead to IO stall on all paths.
      After setting the zfcp device back online using chccwdev,
      the devices with io stall will have a different path checker.
      Devices corresponding to the deleted units are never freed.
      This has the effect that 'slave_destroy' is never called and zfcp
      still thinks that this unit is registered
      (ZFCP_STATUS_UNIT_REGISTERED is still set). Hence the erp
      routine is not called correctly and the unit is not enabled properly.
      
      Do not delete rport and the sdev. Just set the host to block on
      'offline'. Setting host online again will then remove the blocked status
      and everything is fine again.
      Signed-off-by: NMichael Loehr <mloehr2@linux.vnet.ibm.com>
      Signed-off-by: NSwen Schillig <swen@vnet.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      9f28745a
  19. 24 9月, 2006 1 次提交
  20. 07 8月, 2006 1 次提交
  21. 29 5月, 2006 1 次提交
  22. 02 2月, 2006 1 次提交
  23. 20 9月, 2005 1 次提交
  24. 29 8月, 2005 1 次提交
  25. 28 8月, 2005 1 次提交
  26. 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