1. 14 Sep, 2005 2 commits
    • James Bottomley's avatar
      [SCSI] fix sym scsi boot hang · 59897dad
      James Bottomley authored
      On Wed, 2005-09-14 at 18:06 +1000, Anton Blanchard wrote:
      > And in particular it looks like the scsi_unprep_request in
      > scsi_queue_insert is causing it. The following patch fixes the boot
      > problems on the vscsi machine:
      OK, my fault.  Your fix is almost correct .. I was going to do this
      eventually, honest, because there's no need to unprep and reprep a
      command that comes in through scsi_queue_insert().
      However, I decided to leave it in to exercise the scsi_unprep_request()
      path just to make sure it was working.  What's happening, I think, is
      that we also use this path for retries.  Since we kill and reget the
      command each time, the retries decrement is never seen, so we're
      retrying forever.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • Timothy Thelin's avatar
      [SCSI] scsi: sd, sr, st, and scsi_lib all fail to copy cmd_len to new cmd · 186d330e
      Timothy Thelin authored
      This fixes an issue in scsi command initialization from a request
      where sd, sr, st, and scsi_lib all fail to copy the request's
      cmd_len to the scsi command's cmd_len field.
      Signed-off-by: default avatarTimothy Thelin <timothy.thelin@wdc.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  2. 10 Sep, 2005 1 commit
  3. 09 Sep, 2005 3 commits
    • James Bottomley's avatar
      [SCSI] SCSI core: fix leakage of scsi_cmnd's · 788ce43a
      James Bottomley authored
      Actually, just one problem and one cosmetic fix:
      1) We need to dequeue for the loop and kill case (it seems easiest
      simply to dequeue in the scsi_kill_request() routine)
      2) There's no real need to drop the queue lock.  __scsi_done() is lock
      agnostic, so since there's no requirement, let's just leave it in to
      avoid any locking issues.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James Bottomley's avatar
      [SCSI] SCSI core: fix leakage of scsi_cmnd's · e91442b6
      James Bottomley authored
      From: 	Alan Stern <stern@rowland.harvard.edu>
      This patch (as559b) adds a new routine, scsi_unprep_request, which
      gets called every place a request is requeued.  (That includes
      scsi_queue_insert as well as scsi_requeue_command.)  It also changes
      scsi_kill_requests to make it call __scsi_done with result equal to
      DID_NO_CONNECT << 16.  (I'm not sure if it's necessary to call
      scsi_init_cmd_errh here; maybe you can check on that.)  Finally, the
      patch changes the return value from scsi_end_request, to avoid
      returning a stale pointer in the case where the request was requeued.
      Fortunately the return value is used in only place, and the change
      actually simplified it.
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Rejections fixed up and
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • Neil Brown's avatar
      [SCSI] fix possible deadlock in scsi_lib.c · 286f3e13
      Neil Brown authored
        If a filesystem, while writing out data, decides that it is good
      to issue a cache flush on a SCSI drive (or other 'sd' device), it will
      call blkdev_issue_flush which calls ->issue_flush_fn which is
      This calls sd_issue_flush which calls sd_sync_cache, which calls
      This will (as sshdr != NULL) call
      If memory is tight, the presence of GFP_KERNEL may cause write
      requests to be sent to some filesystem to free up memory, however if
      that filesystem is waiting for the issue_flush_fn to complete, you
      could get a deadlock.
      I wonder if it might be more appropriate to use GFP_NOIO as in the
      following patch.
      I wonder if it might be even more appropriate to cope better with a
      kmalloc failure, especially as in this use, sd_sync_cache only will
      use the sense information to print out a more informative error
      Signed-off-by: default avatarNeil Brown <neilb@suse.de>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  4. 06 Sep, 2005 1 commit
    • James Bottomley's avatar
      [SCSI] quieten messages on scsi_execute commands · 3173d8c3
      James Bottomley authored
      scsi_io_completion() can be a bit noisy about certain conditions.
      Previously this wasn't a problem for internally generated commands,
      since they never hit it.  However, since we do all SCSI commands via
      bios, now they do.  user CD testers like magicdev are now getting not
      ready messages every time they touch the CD to see if there's anything
      in it.
      Fix this by making all scsi_execute commands REQ_QUIET and making
      scsi_finish_io() not say anything for REQ_QUIET.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  5. 28 Aug, 2005 8 commits
  6. 30 Jul, 2005 1 commit
  7. 14 Jul, 2005 1 commit
  8. 28 Jun, 2005 1 commit
  9. 26 Jun, 2005 3 commits
  10. 24 Jun, 2005 1 commit
  11. 20 May, 2005 5 commits
  12. 18 Apr, 2005 2 commits
  13. 16 Apr, 2005 4 commits