1. 04 Sep, 2005 8 commits
  2. 30 Aug, 2005 3 commits
    • James Bottomley's avatar
      [SCSI] embryonic RAID class · 61a7afa2
      James Bottomley authored
      The idea behind a RAID class is to provide a uniform interface to all
      RAID subsystems (both hardware and software) in the kernel.
      To do that, I've made this class a transport class that's entirely
      subsystem independent (although the matching routines have to match per
      subsystem, as you'll see looking at the code).  I put it in the scsi
      subdirectory purely because I needed somewhere to play with it, but it's
      not a scsi specific module.
      I used a fusion raid card as the test bed for this; with that kind of
      card, this is the type of class output you get:
      jejb@titanic> ls -l /sys/class/raid_devices/20\:0\:0\:0/
      total 0
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 component-0 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:0/20:1:0:0/
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 component-1 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:1/20:1:1:0/
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 device -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:0:0/20:0:0:0/
      -r--r--r--  1 root root 16384 Aug 16 17:21 level
      -r--r--r--  1 root root 16384 Aug 16 17:21 resync
      -r--r--r--  1 root root 16384 Aug 16 17:21 state
      So it's really simple: for a SCSI device representing a hardware raid,
      it shows the raid level, the array state, the resync % complete (if the
      state is resyncing) and the underlying components of the RAID (these are
      exposed in fusion on the virtual channel 1).
      As you can see, this type of information can be exported by almost
      anything, including software raid.
      The more difficult trick, of course, is going to be getting it to
      perform configuration type actions with writable attributes.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James Bottomley's avatar
      [SCSI] attribute container final klist fixes · 2b7d6a8c
      James Bottomley authored
      Since the attribute container deletes from a klist while it's walking
      it, it is vulnerable to the problem (and fix) here:
      The attached fixes this (but won't compile without the above).
      It also fixes the logical reversal in the traversal loop which meant
      that we were never actually traversing the loop to hit this bug in the
      first place.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James Bottomley's avatar
      [SCSI] correct attribute_container list usage · 53c165e0
      James Bottomley authored
      One of the changes in the attribute_container code in the scsi-misc tree
      was to add a lock to protect the list of devices per container.  This,
      unfortunately, leads to potential scheduling while atomic problems if
      there's a sleep in the function called by a trigger.
      The correct solution is to use the kernel klist infrastructure instead
      which allows lockless traversal of a list.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  3. 28 Aug, 2005 7 commits
  4. 15 Aug, 2005 3 commits
  5. 14 Aug, 2005 2 commits
  6. 13 Aug, 2005 1 commit
  7. 12 Aug, 2005 11 commits
  8. 09 Aug, 2005 1 commit
  9. 08 Aug, 2005 4 commits
    • Dave Jones's avatar
      [SCSI] blacklist addition. · 0d7323c8
      Dave Jones authored
      When run on a kernel that scans all LUNs, a certain crappy
      scsi scanner reports the same LUN over and over..
      Aparently they were so shamed by this, they chose to remain
      anonymous. Though it seems the blacklist code handles
      anonymous vendors just fine.
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • Mark Haverkamp's avatar
      [SCSI] aacraid: adapter support update · 8e87c2f1
      Mark Haverkamp authored
      Received from Mark Salyzyn
      This patch adds the product ID for the ICP9067MA adapter.
      The entries for the ICP9085LI, ICP5085BR, IBM8k & ASR4810SAS were
      incorrect and would not initialize the adapters correctly.
      Signed-off-by: default avatarMark Haverkamp <markh@osdl.org>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James Bottomley's avatar
      [SCSI] add global timeout to the scsi mid-layer · b21a4138
      James Bottomley authored
      There are certain rogue devices (and the aic7xxx driver) that return
      BUSY or QUEUE_FULL forever.  This code will apply a global timeout (of
      the total number of retries times the per command timer) to a given
      command.  If it is exceeded, the command is completed regardless of its
      The patch also removes the unused field in the command: timeout and
      This solves the problem of detecting an endless loop in the mid-layer
      because of BUSY/QUEUE_FULL bouncing, but will not recover the device.
      In the aic7xxx case, the driver can be recovered by sending a bus reset,
      so possibly this should be tied into the error handler?
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • Kai Makisara's avatar
      [SCSI] drivers/scsi/st.c: add reference count and related fixes · f03a5670
      Kai Makisara authored
      I have rediffed the patch against 2.6.13-rc5, done a couple of cosmetic
      cleanups, and run some tests.  Brian King has acknowledged that it fixes the
      problems he has seen. Seems mature enough for inclusion into 2.6.14 (or
      Nate's explanation of the changes:
      I've attached patches against 2.6.13rc2. These are basically identical
      to my earlier patches, as I found that all issues I'd seen in earlier
      kernels still existed in this kernel.
      To summarize, the changes are: (more details in my original email)
      - add a kref to the scsi_tape structure, and associate reference
      counting stuff
      - set sr_request->end_io = blk_end_sync_rq so we get notified when an IO
      is rejected when the device goes away
      - check rq_status when IOs complete, else we don't know that IOs
      rejected for a dead device in fact did not complete
      - change last_SRpnt so it's set before an async IO is issued (in case
      st_sleep_done is bypassed)
      - fix a bogus use of last_SRpnt in st_chk_result
      Signed-off-by: default avatarNate Dailey <nate.dailey@stratus.com>
      Signed-off-by: default avatarKai Makisara <kai.makisara@kolumbus.fi>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>