15 Dec, 2011

4 commits


07 Nov, 2011

1 commit

  • * 'modsplit-Oct31_2011' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux: (230 commits)
    Revert "tracing: Include module.h in define_trace.h"
    irq: don't put module.h into irq.h for tracking irqgen modules.
    bluetooth: macroize two small inlines to avoid module.h
    ip_vs.h: fix implicit use of module_get/module_put from module.h
    nf_conntrack.h: fix up fallout from implicit moduleparam.h presence
    include: replace linux/module.h with "struct module" wherever possible
    include: convert various register fcns to macros to avoid include chaining
    crypto.h: remove unused crypto_tfm_alg_modname() inline
    uwb.h: fix implicit use of asm/page.h for PAGE_SIZE
    pm_runtime.h: explicitly requires notifier.h
    linux/dmaengine.h: fix implicit use of bitmap.h and asm/page.h
    miscdevice.h: fix up implicit use of lists and types
    stop_machine.h: fix implicit use of smp.h for smp_processor_id
    of: fix implicit use of errno.h in include/linux/of.h
    of_platform.h: delete needless include
    acpi: remove module.h include from platform/aclinux.h
    miscdevice.h: delete unnecessary inclusion of module.h
    device_cgroup.h: delete needless include
    net: sch_generic remove redundant use of
    net: inet_timewait_sock doesnt need
    ...

    Fix up trivial conflicts (other header files, and removal of the ab3550 mfd driver) in
    - drivers/media/dvb/frontends/dibx000_common.c
    - drivers/media/video/{mt9m111.c,ov6650.c}
    - drivers/mfd/ab3550-core.c
    - include/linux/dmaengine.h

    Linus Torvalds
     

03 Nov, 2011

1 commit


01 Nov, 2011

1 commit


31 Oct, 2011

1 commit

  • This patch validates sdev pointer in scsi_dh_activate before proceeding further.

    Without this check we might see the panic as below. I have seen this
    panic multiple times..

    Call trace:

    #0 [ffff88007d647b50] machine_kexec at ffffffff81020902
    #1 [ffff88007d647ba0] crash_kexec at ffffffff810875b0
    #2 [ffff88007d647c70] oops_end at ffffffff8139c650
    #3 [ffff88007d647c90] __bad_area_nosemaphore at ffffffff8102dd15
    #4 [ffff88007d647d50] page_fault at ffffffff8139b8cf
    [exception RIP: scsi_dh_activate+0x82]
    RIP: ffffffffa0041922 RSP: ffff88007d647e00 RFLAGS: 00010046
    RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000000093c5
    RDX: 00000000000093c5 RSI: ffffffffa02e6640 RDI: ffff88007cc88988
    RBP: 000000000000000f R8: ffff88007d646000 R9: 0000000000000000
    R10: ffff880082293790 R11: 00000000ffffffff R12: ffff88007cc88988
    R13: 0000000000000000 R14: 0000000000000286 R15: ffff880037b845e0
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0000
    #5 [ffff88007d647e38] run_workqueue at ffffffff81060268
    #6 [ffff88007d647e78] worker_thread at ffffffff81060386
    #7 [ffff88007d647ee8] kthread at ffffffff81064436
    #8 [ffff88007d647f48] kernel_thread at ffffffff81003fba

    Signed-off-by: Babu Moger
    Cc: stable@kernel.org
    Signed-off-by: James Bottomley

    Moger, Babu
     

16 Oct, 2011

1 commit


22 Sep, 2011

2 commits


31 Aug, 2011

7 commits


28 Jul, 2011

1 commit

  • rdac hardware handler assumes that there is one-to-one relation ship
    between the host and the controller w.r.t lun. IOW, it does not
    support "multiple storage partitions" within a storage.

    Example:
    HBA1 and HBA2 see lun 0 and 1 in storage A (1)
    HBA3 and HBA4 see lun 0 and 1 in storage A (2)
    HBA5 and HBA6 see lun 0 and 1 in storage A (3)

    luns 0 and 1 in (1), (2) and (3) are totally different.

    But, rdac handler treats the lun 0s (and lun 1s) as the same when
    sending a mode select to the controller, which is wrong.

    This patch makes the rdac hardware handler associate HBA and the
    storage w.r.t lun (and not the host itself).

    Signed-off-by: Chandra Seetharaman
    Signed-off-by: James Bottomley

    Chandra Seetharaman
     

27 Jul, 2011

1 commit

  • rdac hardware handler uses "Subsystem Identifier" from C4 inquiry page
    to uniquely identify a storage. The problem with that is that if any
    any of the bytes are non-ascii, subsys_id will all be spaces (hex
    0x20). This creates lot of problems especially when there are multiple
    rdac storages are connected to the server.

    Use "Storage Array Unique Identifier" from C8 inquiry page, which is the
    world wide unique identifier for the storage array, to uniquely identify
    the storage.

    Signed-off-by: Chandra Seetharaman
    Signed-off-by: James Bottomley

    Chandra Seetharaman
     

21 Jul, 2011

1 commit

  • All these are instances of
    #define NAME value;
    or
    #define NAME(params_opt) value;

    These of course fail to build when used in contexts like
    if(foo $OP NAME)
    while(bar $OP NAME)
    and may silently generate the wrong code in contexts such as
    foo = NAME + 1; /* foo = value; + 1; */
    bar = NAME - 1; /* bar = value; - 1; */
    baz = NAME & quux; /* baz = value; & quux; */

    Reported on comp.lang.c,
    Message-ID:
    Initial analysis of the dangers provided by Keith Thompson in that thread.

    There are many more instances of more complicated macros having unnecessary
    trailing semicolons, but this pile seems to be all of the cases of simple
    values suffering from the problem. (Thus things that are likely to be found
    in one of the contexts above, more complicated ones aren't.)

    Signed-off-by: Phil Carmody
    Signed-off-by: Jiri Kosina

    Phil Carmody
     

21 May, 2011

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6: (110 commits)
    [SCSI] qla2xxx: Refactor call to qla2xxx_read_sfp for thermal temperature.
    [SCSI] qla2xxx: Unify the read/write sfp mailbox command routines.
    [SCSI] qla2xxx: Clear complete initialization control block.
    [SCSI] qla2xxx: Allow an override of the registered maximum LUN.
    [SCSI] qla2xxx: Add host number in reset and quiescent message logs.
    [SCSI] qla2xxx: Correctly read sfp single byte mailbox register.
    [SCSI] qla2xxx: Add qla82xx_rom_unlock() function.
    [SCSI] qla2xxx: Log if qla82xx firmware fails to load from flash.
    [SCSI] qla2xxx: Use passed in host to initialize local scsi_qla_host in queuecommand function
    [SCSI] qla2xxx: Correct buffer start in edc sysfs debug print.
    [SCSI] qla2xxx: Update firmware version after flash update for ISP82xx.
    [SCSI] qla2xxx: Fix hang during driver unload when vport is active.
    [SCSI] qla2xxx: Properly set the dsd_list_len for dsd_chaining in cmd type 6.
    [SCSI] qla2xxx: Fix virtual port failing to login after chip reset.
    [SCSI] qla2xxx: Fix vport delete hang when logins are outstanding.
    [SCSI] hpsa: Change memset using sizeof(ptr) to sizeof(*ptr)
    [SCSI] ipr: Rate limit DMA mapping errors
    [SCSI] hpsa: add P2000 to list of shared SAS devices
    [SCSI] hpsa: do not attempt PCI power management reset method if we know it won't work.
    [SCSI] hpsa: remove superfluous sleeps around reset code
    ...

    Linus Torvalds
     

02 May, 2011

1 commit

  • The SCSI ALUA handler currently fails to attach to devices
    reporting an UNAVAILABLE/OFFLINE AAS. But given that an
    UNAVAILABLE/OFFLINE AAS can transition to other states
    like ACTIVE/OPTIMIZED, ACTIVE/NON-OPTIMIZED, etc. as per
    SPC4, this ALUA handler behavior should be rectified so
    as to attach to devices which also report an
    UNAVAILABLE/OFFLINE AAS.

    Signed-off-by: Martin George
    Reviewed-by: Mike Christie
    Signed-off-by: James Bottomley

    Martin George
     

01 May, 2011

3 commits

  • Based on the operating modes, handler decides whether to send mode
    select or not. Purpose here is to reduce io-shipping as much as
    possible whenever there is an option.

    Signed-off-by: Babu Moger
    Reviewed-by: Yanling Qi
    Reviewed-by: Sudhir Dachepalli
    Reviewed-by: Somasundaram Krishnasamy
    Reviewed-by: Bob Stankey
    Reviewed-by: Vijay Chauhan
    Signed-off-by: James Bottomley

    Moger, Babu
     
  • This patch detects different operating RDAC modes during the
    discovery. It also collects the information about the preferred path.

    Signed-off-by: Babu Moger
    Reviewed-by: Yanling Qi
    Reviewed-by: Sudhir Dachepalli
    Reviewed-by: Somasundaram Krishnasamy
    Reviewed-by: Bob Stankey
    Reviewed-by: Vijay Chauhan
    Signed-off-by: James Bottomley

    Moger, Babu
     
  • This patch adds definitions to support for different operating modes
    for LSI rdac storage. Currently, rdac support 3 operation modes.

    1. RDAC mode(legacy)
    2. AVT mode
    3. IOSHIP mode

    These definitions are used while activating the path(rdac_activate).

    Signed-off-by: Babu Moger
    Reviewed-by: Yanling Qi
    Reviewed-by: Sudhir Dachepalli
    Reviewed-by: Somasundaram Krishnasamy
    Reviewed-by: Bob Stankey
    Reviewed-by: Vijay Chauhan
    Signed-off-by: James Bottomley

    Moger, Babu
     

25 Apr, 2011

1 commit


31 Mar, 2011

1 commit


15 Mar, 2011

1 commit


13 Feb, 2011

4 commits


25 Jan, 2011

6 commits

  • Previously we were using strncmp in order to avoid having to include
    whitespace in the devlist, but this means "HSV1000" matches a device
    list entry that says "HSV100", which is wrong. This patch changes
    scsi_dh.c to use scsi_devinfo's matching functions instead, since they
    handle these cases correctly.

    Signed-off-by: James Bottomley

    Peter Jones
     
  • Currently NetApp's VID/PID details in the INQUIRY response shows up as
    'NETAPP' and 'LUN'. With upcoming scalable SAN ONTAP version on NetApp
    controllers, the PID entry alone is being modified to 'LUN C-Mode' (to
    distinguish current ONTAP LUNs from scalable ONTAP LUNs).

    'LUN' would still suffice for matching 'LUN C-Mode' but best to
    explicitly add these new NetApp LUNs to the device list.

    Reported-by: Martin George
    Acked-by: Mike Christie
    Signed-off-by: Mike Snitzer
    Signed-off-by: James Bottomley

    Mike Snitzer
     
  • Adds Promise VTrak devices to the ALUA device handler.

    Signed-off-by: Ilgu Hong
    Signed-off-by: Joseph Gruher
    Signed-off-by: Mike Snitzer
    Signed-off-by: James Bottomley

    Ilgu Hong
     
  • Initialize stpg_endio() 'err' to SCSI_DH_OK and only change it to
    SCSI_DH_IO accordingly. This allows the switching of target group state
    to be properly reported when no error has occurred.

    Signed-off-by: Joseph Gruher
    Signed-off-by: Ilgu Hong
    Signed-off-by: Mike Snitzer
    Signed-off-by: James Bottomley

    Joseph Gruher
     
  • The use of blk_execute_rq_nowait() implies __blk_put_request() is needed
    in stpg_endio() rather than blk_put_request() -- blk_finish_request() is
    called with queue lock already held.

    Signed-off-by: Joseph Gruher
    Signed-off-by: Ilgu Hong
    Signed-off-by: Mike Snitzer
    Cc: stable@kernel.org
    Signed-off-by: James Bottomley

    Joseph Gruher
     
  • submit_stpg() will always return failure so alua_activate() will report
    failure via dm-multipath callback function. Even though the stpg fired
    successfuly dm-multipath does not know and always fails to change the
    valid path.

    By returning SCSI_DH_OK we're now skipping alua_activate()'s call to
    activate_complete 'fn'. But this is fine because stpg_endio() will call
    it via h->callback_fn().

    Signed-off-by: Joseph Gruher
    Signed-off-by: Ilgu Hong
    Signed-off-by: Mike Snitzer
    Signed-off-by: James Bottomley

    Joseph Gruher
     

22 Dec, 2010

1 commit

  • Currently, when scsi_dh_activate() returns with an error
    (e.g. SCSI_DH_NOSYS) the activate_complete callback is not called and
    the error is not propagated to DM mpath.

    When a SCSI device attached to a device handler is deleted, userland
    processes currently performing I/O on the device will have their I/O
    hang forever.

    - Set SCSI_DH_NOSYS error when the handler is in the process of being
    deleted (e.g. the SCSI device is in a SDEV_CANCEL or SDEV_DEL state).

    - Set SCSI_DH_DEV_OFFLINED error when device is in SDEV_OFFLINE state.

    - Call the activate_complete callback function directly from
    scsi_dh_activate if an error has been set (when either the scsi_dh
    internal data has already been deleted or is in the process of being
    deleted).

    The patch was tested in an iSCSI environment, RDAC H/W handler and
    multipath. In the following reproduction process, dd will I/O hang
    forever and the only way to release it will be to reboot the machine:
    1) Perform I/O on a multipath device:
    dd if=/dev/dm-0 of=/dev/zero bs=8k count=1000000 &
    2) Delete all slave SCSI devices contained in the mpath device:
    I) In an iSCSI environment, the easiest way to do this is by
    stopping iSCSI:
    /etc/init.d/iscsi stop
    II) Another way to delete the devices is by applying the following
    bash scriptlet:
    dm_devs=$(ls /sys/block/ | grep dm- | xargs)
    for dm_dev in $dm_devs; do
    devices=$(ls /sys/block/$dm_dev/slaves)
    for device in $devices; do
    echo 1 > /sys/block/$device/device/delete
    done
    done

    NOTE: when DM mpath's fail_path uses blk_abort_queue this scsi_dh change
    isn't strictly required. However, DM mpath's call to blk_abort_queue
    will soon be reverted because it has proven to be unsafe due to a race
    (between blk_abort_queue and scsi_request_fn) that can lead to list
    corruption. Therefore we cannot rely on blk_abort_queue via fail_path,
    but even if we could this scsi_dh change is still preferrable.

    Signed-off-by: Menny Hamburger
    Signed-off-by: Mike Snitzer
    Reviewed-by: Babu Moger
    Signed-off-by: James Bottomley

    Menny Hamburger