- 15 Jul, 2016 26 commits
-
-
James Smart authored
Copyright updates Signed-off-by:
Dick Kennedy <dick.kennedy@broadcom.com> Signed-off-by:
James Smart <james.smart@broadcom.com> Reviewed-by:
Hannes Reinecke <hare@suse.com> Signed-off-by:
Martin K. Petersen <martin.petersen@oracle.com>
-
James Smart authored
Disable FDMI probing if not connected to a fabric Signed-off-by:
-
James Smart authored
Correct issue with ioremap() call on 32bit kernel Signed-off-by:
-
James Smart authored
Re-organize source for easier driver attribute management Signed-off-by:
-
James Smart authored
Remove global lpfc_sli_mode attribute in leiu of per-hba lpfc_sli_mode Signed-off-by:
-
James Smart authored
Remove global lpfc_delay_discovery attribute in leiu of per-hba lpfc_delay_discovery Signed-off-by:
-
James Smart authored
Remove global lpfc_enable_npiv attribute in leiu of per-hba lpfc_enable_npiv Signed-off-by:
-
James Smart authored
Correct Port reset resulting in FC port going offline Signed-off-by:
-
James Smart authored
Add support for XLane LUN priority Signed-off-by:
-
James Smart authored
Correct RDP response Revision location Signed-off-by:
-
James Smart authored
Re-organize source for easier device-id management Signed-off-by:
-
James Smart authored
Correct FCOE discovery to avoid loss of storage devices after system reboot Signed-off-by:
-
James Smart authored
Fix SLI mode 2 config failure Signed-off-by:
-
James Smart authored
Add MDS Diagnostics Support Signed-off-by:
-
James Smart authored
Add sysfs proc_name support Signed-off-by:
-
James Smart authored
Reject RDP ELS if port has no login Signed-off-by:
-
James Smart authored
Correct Buffer credit descriptor values in RDP response Signed-off-by:
-
James Smart authored
Add recovery from adapter parity errors on some SLI4 adapters Signed-off-by:
-
James Smart authored
Correct RDP response sizing issue Signed-off-by:
-
James Smart authored
Fix Transgression Flag of Optical Element descriptor for RDP on Linux Signed-off-by:
-
Dan Carpenter authored
My static checker complains that we need to unlock on this path. Seems true. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Reviewed-by:
Brian King <brking@linux.vnet.ibm.com> Reviewed-by:
Ewan D. Milne <emilne@redhat.com> Signed-off-by:
-
Hans de Goede authored
Oliver Neukum is taking over uas maintainership from me and Gerd Hoffmann. Cc: Oliver Neukum <oneukum@suse.com> Cc: Gerd Hoffmann <kraxel@redhat.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Oliver Neukum <oneukum@suse.com> Acked-by:
Gerd Hoffmann <kraxel@redhat.com> Signed-off-by:
-
Christoph Hellwig authored
We've had scsi-mq for 2.5 years now, so we can remove the unused flag to disable the code on a per-host basis that was put in for unexpected emergencies during bringup. Signed-off-by:
Christoph Hellwig <hch@lst.de> Reviewed-by:
Bart Van Assche <bart.vanassche@sandisk.com> Signed-off-by:
-
Manjunath M B authored
The code was checking on PA_CONNECTEDRXLANES and PA_CONNECTEDTXLANES attributes to program the Lane#1 attributes. The correct attributes are PA_AVAILRXDATALANES and PA_AVAILTXDATALANES respectively. Signed-off-by:
Manjunath M B <manjumb@synopsys.com> Tested-by:
Joao Pinto <jpinto@synopsys.com> Signed-off-by:
-
Kefeng Wang authored
The _scsih_pci_mmio_enabled called if scsih_pci_error_detected returns PCI_ERS_RESULT_CAN_RECOVER, at this point, read/write to the device still works, no need to reset slot. Or the mpt3sas_base_map_resources in scsih_pci_slot_reset will fail, and iounamp ioc->chip, then we will meet issue when read ioc->chip in mpt3sas_base_get_iocstate from _base_fault_reset_work. Cc: Sathya Prakash <sathya.prakash@broadcom.com> Cc: Chaitra P B <chaitra.basappa@broadcom.com> Cc: Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com> Signed-off-by:
Kefeng Wang <wangkefeng.wang@huawei.com> Acked-by:
Chaitra P B <chaitra.basappa@broadcom.com> Signed-off-by:
-
Johannes Thumshirn authored
qla2xxx first calls request_irq() and then does the setup of the queue entry data needed in the interrupt handlers in when using MSI-X. This could lead to a NULL pointer dereference when an IRQ fires between the request_irq() call and the assignment of the qentry data structure to the rsp->msix field. A possible case for such a race would be in the kdump case when the HBA's IRQs are still enabled but the driver is undergoing a new initialisation and thus is not aware of already activated IRQs in the HBA. Signed-off-by:
Johannes Thumshirn <jthumshirn@suse.de> Reviewed-by:
Himanshu Madhani <himanshu.madhani@qlogic.com> Signed-off-by:
-
- 14 Jul, 2016 10 commits
-
-
Wen Xiong authored
Increase MSIX vectors from 2 to 16 by default. Signed-off-by:
Wen Xiong <wenxiong@linux.vnet.ibm.com> Reviewed-by:
Gabriel Krisman Bertazi <krisman@linux.vnet.ibm.com> Acked-by:
-
Wen Xiong authored
Add the appropriate definitions and table entries for new adapters support. Signed-off-by:
-
Christoph Hellwig authored
The field is only used by the 53c700 driver, so move it into the driver-private device data instead of having it in the common structure. Signed-off-by:
Tomas Henzl <thenzl@redhat.com> Reviewed-by:
-
Sumit Saxena authored
There was an issue reported by Lucz Geza on Dell Perc 6i. As per issue reported, megaraid_sas driver goes into an infinite error reporting loop as soon as there is a change in the status of one of the arrays (degrade, resync online etc ). Below are the error logs reported continuously- Jun 25 08:49:30 ns8 kernel: [ 757.757017] megaraid_sas 0000:02:00.0: DCMD failed/not supported by firmware: megasas_get_pd_list 4115 Jun 25 08:49:30 ns8 kernel: [ 757.778017] megaraid_sas 0000:02:00.0: DCMD failed/not supported by firmware: megasas_get_pd_list 4115 Jun 25 08:49:30 ns8 kernel: [ 757.799017] megaraid_sas 0000:02:00.0: DCMD failed/not supported by firmware: megasas_get_pd_list 4115 Jun 25 08:49:30 ns8 kernel: [ 757.820018] megaraid_sas 0000:02:00.0: DCMD failed/not supported by firmware: megasas_get_pd_list 4115 Jun 25 08:49:30 ns8 kernel: [ 757.841018] megaraid_sas 0000:02:00.0: DCMD failed/not supported by firmware: megasas_get_pd_list 4115 This issue is very much specific to controllers which do not support DCMD- MR_DCMD_PD_LIST_QUERY. In case of any hotplugging/rescanning of drives, AEN thread will be scheduled by driver and fire DCMD- MR_DCMD_PD_LIST_QUERY and if this DCMD is failed then driver will fail this event processing and will not go ahead for further events. This will cause infinite loop of same event getting retried infinitely and causing above mentioned logs. Fix for this problem is: not to fire DCMD MR_DCMD_PD_LIST_QUERY for controllers which do not support it and send DCMD SUCCESS status to AEN function so that it can go ahead with other event processing. Reported-by:
Lucz Geza <geza@lucz.com> Cc: <stable@vger.kernel.org> Signed-off-by:
Sumit Saxena <sumit.saxena@broadcom.com> Reviewed-by:
-
Johannes Thumshirn authored
Use defines from ethtool for 20Gbit and 40Gbit speeds instead of magic numbers. Signed-off-by:
Laurence Oberman <loberman@redhat.com> Signed-off-by:
-
Hannes Reinecke authored
When the FIP mode is changed we need to update the multicast addresses to ensure we get the correct frames. Signed-off-by:
Johannes Thumshirn <jth@kernel.org> Signed-off-by:
-
Hannes Reinecke authored
'->realdev' is always set, so this check is pointless. Signed-off-by:
-
Hannes Reinecke authored
The FIP mode is independent on the FIP state machine, so use a separate enum for that instead of overloading it with state machine values. Signed-off-by:
-
Hannes Reinecke authored
Update to latest FC-BB-6 draft to include FIP VN2VN VLAN notifications and additional flags. Signed-off-by:
-
Chris Leech authored
In the receive path libfc extracts a cpu number from the ox_id in the fiber channel header and uses that to do a per_cpu_ptr conversion. If, for some reason, a frame is received with an invalid ox_id, per_cpu_ptr will return an invalid pointer and the libfc receive path will panic the system trying to use it. I'm currently looking at such a case, and I don't yet know why a cpu number > nr_cpu_ids is appearing in an exchange id. But adding a sanity check in libfc prevents a system panic, and seems like good idea when dealing with frames coming in from the network. Signed-off-by:
Chris Leech <cleech@redhat.com> Acked-by:
-
- 13 Jul, 2016 4 commits
-
-
Sebastian Andrzej Siewior authored
The driver creates its own per-CPU threads which are updated based on CPU hotplug events. It is also possible to use kworkers and remove some of the kthread infrastrucure. The code checked ->thread to decide if there is an active per-CPU thread. By using the kworker infrastructure this is no longer possible (or required). The thread pointer is saved in `kthread' instead of `thread' so anything trying to use thread is caught by the compiler. Currently only the bnx2fc driver is using struct fcoe_percpu_s and the kthread member. After a CPU went offline, we may still enqueue items on the "offline" CPU. This isn't much of a problem. The work will be done on a random CPU. The allocated crc_eof_page page won't be cleaned up. It is probably expected that the CPU comes up at some point so it should not be a problem. The crc_eof_page memory is released of course once the module is removed. This patch was only compile-tested due to -ENODEV. Cc: Vasu Dev <vasu.dev@intel.com> Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com> Cc: "Martin K. Petersen" <martin.petersen@oracle.com> Cc: Christoph Hellwig <hch@lst.de> Cc: fcoe-devel@open-fcoe.org Cc: linux-scsi@vger.kernel.org Signed-off-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Tested-by:
-
Johannes Thumshirn authored
Vasu is going to resign from his maintainer role and I'll take over. Signed-off-by:
Vasu Dev <vasu.dev@intel.com> Signed-off-by:
-
Johannes Thumshirn authored
If there is a dma mapping error snic kfree()s buf right before printing it. Change the order to not accidently trip on memory that's not owned by us anymore. Signed-off-by:
Narsimhulu Musini <nmusini@cisco.com> Reviewed-by:
-
Arnd Bergmann authored
Enabling format checking in dprintk() shows that wd7000_biosparam uses an incorrect format string for sector_t: drivers/scsi/wd7000.c: In function 'wd7000_biosparam': drivers/scsi/wd7000.c:1594:21: error: format '%d' expects argument of type 'int', but argument 3 has type 'sector_t {aka long long unsigned int}' [-Werror=format=] As sector_t can be 32-bit wide, this adds a cast to 'u64' and prints that with the correct format. The change to use no_printk() generally helps with finding this kind of hidden format string bug, and I found that when building with "-Wextra", which warned about an empty else clause in } else dprintk("ok!\n"); Signed-off-by:Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
