Eric Lee / smarc-fsl-linux-kernel

03 Oct, 2011

1 commit

  • 2fc62e2ac   [SCSI] libsas: disable scanning lun > 0 on ata devices ... Browse Code »

    Currently mvsas and pm8001 have custom ->slave_alloc implementations to
    achieve this. Uplevel it for all libsas drivers as isci encounters problems
    with atapi devices when scanning past lun0.

    Just do what Darrick suggested [1], and limit the scan for ata devices.

    [1] http://marc.info/?l=linux-scsi&m=116604101119861&w=2

    Signed-off-by: Dan Williams
    Signed-off-by: James Bottomley

    Dan Williams
     

10 Mar, 2011

1 commit

  • 7eaceacca   block: remove per-queue plugging ... Browse Code »
    86

    Code has been converted over to the new explicit on-stack plugging,
    and delay users have been converted to use the new API for that.
    So lets kill off the old plugging along with aops->sync_page().

    Signed-off-by: Jens Axboe

    Jens Axboe
     

09 Feb, 2010

1 commit

04 Dec, 2009

1 commit

  • af901ca18   tree-wide: fix assorted typos all over the place ... Browse Code »

    That is "success", "unknown", "through", "performance", "[re|un]mapping"
    , "access", "default", "reasonable", "[con]currently", "temperature"
    , "channel", "[un]used", "application", "example","hierarchy", "therefore"
    , "[over|under]flow", "contiguous", "threshold", "enough" and others.

    Signed-off-by: André Goddard Rosa
    Signed-off-by: Jiri Kosina

    André Goddard Rosa
     

23 Aug, 2009

1 commit

21 Jun, 2009

1 commit

11 May, 2009

1 commit

  • 9934c8c04   block: implement and enforce request peek/start/fetch ... Browse Code »

    Till now block layer allowed two separate modes of request execution.
    A request is always acquired from the request queue via
    elv_next_request(). After that, drivers are free to either dequeue it
    or process it without dequeueing. Dequeue allows elv_next_request()
    to return the next request so that multiple requests can be in flight.

    Executing requests without dequeueing has its merits mostly in
    allowing drivers for simpler devices which can't do sg to deal with
    segments only without considering request boundary. However, the
    benefit this brings is dubious and declining while the cost of the API
    ambiguity is increasing. Segment based drivers are usually for very
    old or limited devices and as converting to dequeueing model isn't
    difficult, it doesn't justify the API overhead it puts on block layer
    and its more modern users.

    Previous patches converted all block low level drivers to dequeueing
    model. This patch completes the API transition by...

    * renaming elv_next_request() to blk_peek_request()

    * renaming blkdev_dequeue_request() to blk_start_request()

    * adding blk_fetch_request() which is combination of peek and start

    * disallowing completion of queued (not started) requests

    * applying new API to all LLDs

    Renamings are for consistency and to break out of tree code so that
    it's apparent that out of tree drivers need updating.

    [ Impact: block request issue API cleanup, no functional change ]

    Signed-off-by: Tejun Heo
    Cc: Rusty Russell
    Cc: James Bottomley
    Cc: Mike Miller
    Cc: unsik Kim
    Cc: Paul Clements
    Cc: Tim Waugh
    Cc: Geert Uytterhoeven
    Cc: David S. Miller
    Cc: Laurent Vivier
    Cc: Jeff Garzik
    Cc: Jeremy Fitzhardinge
    Cc: Grant Likely
    Cc: Adrian McMenamin
    Cc: Stephen Rothwell
    Cc: Bartlomiej Zolnierkiewicz
    Cc: Borislav Petkov
    Cc: Sergei Shtylyov
    Cc: Alex Dubov
    Cc: Pierre Ossman
    Cc: David Woodhouse
    Cc: Markus Lidel
    Cc: Stefan Weinhuber
    Cc: Martin Schwidefsky
    Cc: Pete Zaitcev
    Cc: FUJITA Tomonori
    Signed-off-by: Jens Axboe

    Tejun Heo
     

03 Jan, 2009

1 commit

27 Jul, 2008

1 commit

29 Apr, 2008

1 commit

23 Apr, 2008

2 commits

  • 93c20a59a   [SCSI] scsi_transport_sas: fix the lifetime of sas bsg objects ... Browse Code »

    scsi_transport_sas calls blk_cleanup_queue too early for bsg
    queues. If a user holds a sas_host, end_device, or expander device
    open, remove the device, then send a request to it, we get a kernel
    crash. We need to call blk_cleanup_queue in the release callback as we
    do with scsi devices.

    This patch moves blk_cleanup_queue to sas_expander_release and
    sas_end_device_release from sas_bsg_remove. sas_host can't use the
    release callback in struct device so use bsg's release callback.

    Signed-off-by: FUJITA Tomonori
    Signed-off-by: James Bottomley

    FUJITA Tomonori
     
  • 97f46ae45   [SCSI] bsg: add release callback support ... Browse Code »

    This patch adds release callback support, which is called when a bsg
    device goes away. bsg_register_queue() takes a pointer to a callback
    function. This feature is useful for stuff like sas_host that can't
    use the release callback in struct device.

    If a caller doesn't need bsg's release callback, it can call
    bsg_register_queue() with NULL pointer (e.g. scsi devices can use
    release callback in struct device so they don't need bsg's callback).

    With this patch, bsg uses kref for refcounts on bsg devices instead of
    get/put_device in fops->open/release. bsg calls put_device and the
    caller's release callback (if it was registered) in kref_put's
    release.

    Signed-off-by: FUJITA Tomonori
    Signed-off-by: James Bottomley

    FUJITA Tomonori
     

20 Apr, 2008

1 commit

03 Feb, 2008

1 commit

12 Jan, 2008

2 commits

  • 2d507a01d   [SCSI] libsas, bsg: pass errors through correctly ... Browse Code »

    Currently in BSG, errors returned in req->errors aren't passed back to
    the calling programme (either via SG_IO or via read/write). Fix this,
    while preserving the SCSI convention of returning status in
    req->errors.

    Now update libsas to return errors correctly instead of to ignore
    them.

    Acked-by: FUJITA Tomonori
    Signed-off-by: James Bottomley

    James Bottomley
     
  • eb44820c2   [SCSI] Add Documentation and integrate into docbook build ... Browse Code »

    Add Documentation/DocBook/scsi_midlayer.tmpl, add to Makefile, and update
    lots of kerneldoc comments in drivers/scsi/*.

    Updated with comments from Stefan Richter, Stephen M. Cameron,
    James Bottomley and Randy Dunlap.

    Signed-off-by: Rob Landley
    Signed-off-by: James Bottomley

    Rob Landley
     

21 Jul, 2007

2 commits

  • 39dca558a   [SCSI] bsg: make class backlinks ... Browse Code »

    Currently, bsg doesn't make class backlinks (a process whereby you'd get
    a link to bsg in the device directory in the same way you get one for
    sg). This is because the bsg device is uninitialised, so the class
    device has nothing it can attach to. The fix is to make the bsg device
    point to the cdevice of the entity creating the bsg, necessitating
    changing the bsg_register_queue() prototype into a form that takes the
    generic device.

    Acked-by: FUJITA Tomonori
    Signed-off-by: James Bottomley

    James Bottomley
     
  • b6aff6695   [SCSI] scsi_transport_sas: add destructor for bsg ... Browse Code »

    There's currently no destructor for the bsg components. If you insert
    and remove the module, you see the bsg devices building up and up. This
    patch adds the destructor in the correct place in the transport class so
    that the bsg and request queue are removed just before the device
    destruction.

    Acked-by: FUJITA Tomonori
    Signed-off-by: James Bottomley

    James Bottomley
     

19 Jul, 2007

1 commit

18 Feb, 2007

1 commit

28 Jan, 2007

2 commits

  • 214349664   [SCSI] libsas: Check return values of sysfs_create_link ... Browse Code »

    Get rid of: "warning: ignoring return value of sysfs_create_link..."

    Signed-off-by: Darrick J. Wong
    Signed-off-by: James Bottomley

    Darrick J. Wong
     
  • 6f63caae2   [SCSI] libsas: Clean up discovery failure handler code ... Browse Code »

    sas_rphy_delete does two things: it removes the sas_rphy from the transport
    layer and frees the sas_rphy. This can be broken down into two functions,
    sas_rphy_remove and sas_rphy_free; sas_rphy_remove is of interest to
    sas_discover_root_expander because it calls functions that require
    sas_rphy_add as a prerequisite and can fail (namely sas_discover_expander).
    In that case, sas_discover_root_expander needs to be able to undo the effects
    of sas_rphy_add yet leave the job of freeing the sas_rphy to the caller of
    sas_discover_root_expander.

    This patch also removes some unnecessary code from sas_discover_end_dev
    to eliminate an unnecessary cycle of sas_notify_lldd_gone/found for SAS
    devices, thus eliminating a sas_rphy_remove call (and fixing a race condition
    where a SCSI target scan can come in between the gone and found call).
    It also moves the sas_rphy_free calls into sas_discover_domain and
    sas_ex_discover_end_dev to complement the sas_rphy_allocation via
    sas_get_port_device.

    This patch does not change the semantics of sas_rphy_delete.

    Signed-off-by: Darrick J. Wong
    Signed-off-by: James Bottomley

    Darrick J. Wong
     

27 Jan, 2007

1 commit

14 Jan, 2007

3 commits

04 Dec, 2006

1 commit

08 Sep, 2006

1 commit

28 Aug, 2006

1 commit

  • f4ad7b580   [SCSI] scsi_transport_sas: remove local_attached flag ... Browse Code »

    This flag denotes local attachment of the phy. There are two problems
    with it:

    1) It's actually redundant ... you can get the same information simply
    by seeing whether a host is the phys parent
    2) we condition a lot of phy parameters on it on the false assumption
    that we can only control local phys. I'm wiring up phy resets in the
    aic94xx now, and it will be able to reset non-local phys as well.

    I fixed 2) by moving the local check into the reset and stats function
    of the mptsas, since that seems to be the only HBA that can't
    (currently) control non-local phys.

    Signed-off-by: James Bottomley

    James Bottomley
     

12 Jul, 2006

2 commits

09 Jul, 2006

1 commit

  • c9fefeb26   [SCSI] scsi_transport_sas: add unindexed ports ... Browse Code »

    Some SAS HBAs don't want to go to the trouble of tracking port numbers,
    so they'd simply like to say "add this port and give it a number".
    This is especially beneficial from the hotplug point of view, since
    tracking ports and the available number space can be a real pain.

    The current implementation uses an incrementing number per expander to
    add the port on. However, since there can never be more ports than
    there are phys, a later implementation will try to be more intelligent
    about this.

    Signed-off-by: James Bottomley

    James Bottomley
     

29 Jun, 2006

1 commit

12 Jun, 2006

1 commit

11 Jun, 2006

1 commit

10 Jun, 2006

1 commit

20 May, 2006

2 commits

  • 9f434d4f8   [SCSI] scsi_transport_sas: make write attrs writeable ... Browse Code »

    A couple write attributes in sas transport layer have a small
    bug that prevents them from being written to. Those
    attributes are the link_reset and write_reset. This is due
    the store field being set to NULL.

    Signed-off-by: Eric Moore
    Signed-off-by: James Bottomley

    Eric Moore
     
  • 6d99a3f37   [SCSI] scsi_transport_sas; fix user_scan ... Browse Code »

    the user_scan() callback currently has the potential to identify the
    wrong device in the presence of expanders. This is because it finds
    the first device with a matching target_id, which might be an
    expander. Fix this by making it look specifically for end devices.

    Signed-off-by: James Bottomley

    James Bottomley
     

15 Apr, 2006

1 commit

13 Apr, 2006

1 commit