[cciss: PATCH 00/17] fix scan_thread, sysfs stuff,LUN addressing problem

[Stephen M. Cameron]

The following series cleans up the broken scan_thread code,
allows triggering of the scan_thread via sysfs, dynamically
allocates the struct device for each logical drive as needed
instead of all at once at driver init time, fixes a bug in
logical drive addressing (seen on MSA2012), and adds lunid,
raid_level, and usage_count attributes in sysfs for each
logical drive.

---

Andrew Patterson (3):
      Allow triggering of rescan of logical drive topology via sysfs entry
      Use one scan thread per controller and fix hang during rmmod
      Remove sysfs entries for logical drives on driver cleanup.

Stephen M. Cameron (14):
      Add usage_count attribute to each logical drive in /sys
      Add a "raid_level" attribute to each logical drive in /sys
      Add lunid attribute to each logical drive in /sys
      Preserve all 8 bytes of LUN ID for logical drives.
      Silence noisy per-disk messages output by cciss_read_capacity
      Fix excessive gendisk freeing bug on driver unload.
      Fix usage_count check in rebuild_lun_table when triggered via sysfs.
      Clear all sysfs-exposed data for deleted logical drives.
      Handle special case for sysfs attributes of the first logical drive.
      Handle cases when cciss_add_disk fails.
      Handle failure of blk_init_queue gracefully in cciss_add_disk.
      Rearrange logical drive sysfs code to make the "changing a disk" path work.
      Dynamically allocate struct device for each logical drive as needed.
      Remove some unused code in rebuild_lun_table()


 .../ABI/testing/sysfs-bus-pci-devices-cciss        |   28 +
 drivers/block/cciss.c                              |  551 +++++++++++++++-----
 drivers/block/cciss.h                              |   11 
 3 files changed, 461 insertions(+), 129 deletions(-)

-- 
-- steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/