1. 04 3月, 2006 4 次提交
  2. 02 3月, 2006 3 次提交
  3. 01 3月, 2006 1 次提交
  4. 28 2月, 2006 8 次提交
  5. 27 2月, 2006 1 次提交
  6. 26 2月, 2006 2 次提交
  7. 23 2月, 2006 1 次提交
  8. 21 2月, 2006 4 次提交
    • T
      [PATCH] libata: kill ata_dev_reread_id() · ba70d061
      Tejun Heo 提交于
      Kill now-unused ata_dev_reread_id().
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      ba70d061
    • T
      [PATCH] libata: separate out ata_dev_read_id() · 49016aca
      Tejun Heo 提交于
      Separate out ata_dev_read_id() from ata_dev_identify().  This is the
      first half of splitting ata_dev_identify().  ata_dev_read_id() will
      also be used for revalidation.  This patch does not make any behavior
      change.
      
      ata_dev_read_id() doesn't modify any of libata-internal data
      structures.  It simply reads IDENTIFY page and returns error code on
      failure.  INIT_DEV_PARAMS and EDD wrong class code are also handled by
      this function.
      
      Re-reading IDENTIFY after INIT_DEV_PARAMS is performed by jumping to
      retry: instead of calling ata_dev_reread_id().  This is done because
      1. there's retry label anyway 2. ata_dev_reread_id() cannot be used
      anywhere else so there's no reason to keep it.
      
      This function is probably the place to set transfer mode to PIO0
      before IDENTIFY.  However, reset -> identify -> init_dev_params order
      should be kept for pre-ATA4 devices so we cannot set transfer mode
      before IDENTIFY for them.  How do we know if a device is post-ATA4
      before IDENTIFY?
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      49016aca
    • T
      [PATCH] libata: make ata_sg_setup_one() trim zero length sg · 2e242fa9
      Tejun Heo 提交于
      This patch makes ata_sg_setup_one() trim sg entry (thus making
      qc->n_elem zero) if padding results in zero length sg entry.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      2e242fa9
    • T
      [PATCH] libata: fix WARN_ON() condition in *_fill_sg() · 9ae61c6c
      Tejun Heo 提交于
      For ATAPI commands, padding can reduce qc->n_elem by one and thus to
      zero making assert(qc->n_elem > 0)'s in ata_fill_sg() and qs_fill_sg()
      fail for legal commands.  This patch fixes the assert()'s to take
      qc->pad_len into account.
      
      Although the condition check seems a bit excessive, as this part of
      code isn't still stable yet, I think it's worth to keep those.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      9ae61c6c
  9. 20 2月, 2006 5 次提交
  10. 18 2月, 2006 3 次提交
  11. 15 2月, 2006 2 次提交
    • J
      [SCSI] fix wrong context bugs in SCSI · 65110b21
      James Bottomley 提交于
      There's a bug in releasing scsi_device where the release function
      actually frees the block queue.  However, the block queue release
      calls flush_work(), which requires process context (the scsi_device
      structure may release from irq context).  Update the release function
      to invoke via the execute_in_process_context() API.
      
      Also clean up the scsi_target structure releasing via this API.
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      65110b21
    • J
      [PATCH] add scsi_execute_in_process_context() API · faead26d
      James Bottomley 提交于
      We have several points in the SCSI stack (primarily for our device
      functions) where we need to guarantee process context, but (given the
      place where the last reference was released) we cannot guarantee this.
      
      This API gets around the issue by executing the function directly if
      the caller has process context, but scheduling a workqueue to execute
      in process context if the caller doesn't have it.  Unfortunately, it
      requires memory allocation in interrupt context, but it's better than
      what we have previously.  The true solution will require a bit of
      re-engineering, so isn't appropriate for 2.6.16.
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      faead26d
  12. 13 2月, 2006 6 次提交