Hi James,
Please apply the following patches for 3.9-rc.
Thanks,
~Saurav
Arun Easi (1):
qla2xxx: Fix crash during firmware dump procedure.
Joe Carnuccio (1):
Revert qla2xxx: Add setting of driver version string for vendor
application.
Saurav Kashyap (3):
qla2xxx: Update copyright
From: Arun Easi arun.e...@qlogic.com
System crashes, in initiator mode operation, with
qla2xxx_copy_atioqueues() in stack trace when firmware dump is
attempted.
Check for atio_q_length alone does not indicate if atio_ring is
allocated, make explicit check of atio_ring to avoid the crash.
Signed-off-by: Giridhar Malavali giridhar.malav...@qlogic.com
Signed-off-by: Saurav Kashyap saurav.kash...@qlogic.com
---
drivers/scsi/qla2xxx/qla_attr.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_attr.c b/drivers/scsi/qla2xxx/qla_attr.c
Signed-off-by: Giridhar Malavali giridhar.malav...@qlogic.com
Signed-off-by: Saurav Kashyap saurav.kash...@qlogic.com
---
drivers/scsi/qla2xxx/qla_version.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_version.h
From: Joe Carnuccio joe.carnuc...@qlogic.com
The original patch was not covering all the adapters and firmwares.
This commit reverts 3a11711ad00caebee07e262d188cea66f3473c38.
Signed-off-by: Joe Carnuccio joe.carnuc...@qlogic.com
Signed-off-by: Saurav Kashyap saurav.kash...@qlogic.com
---
Signed-off-by: Giridhar Malavali giridhar.malav...@qlogic.com
Signed-off-by: Saurav Kashyap saurav.kash...@qlogic.com
---
Documentation/scsi/LICENSE.qla2xxx |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/scsi/LICENSE.qla2xxx
On 03/23/13 12:28, Wanlong Gao wrote:
+static struct virtio_scsi_vq *virtscsi_pick_vq(struct virtio_scsi *vscsi,
+ struct virtio_scsi_target_state
*tgt)
+{
+ struct virtio_scsi_vq *vq;
+ unsigned long flags;
+ u32 queue_num;
+
+
On 3/16/2013 3:37 PM, Dan Carpenter wrote:
We need to store PROTO_ERR_IMPL_LOGO (26) things here, but the
first element isn't used so the array should have 27 elements.
This matches fwevt_to_rnevt[] which has 27 elements.
The patch solves a Smatch static checker warning on my system:
-Original Message-
From: Mike Christie micha...@cs.wisc.edu
Date: Saturday 23 March 2013 11:58 AM
To: Vikas vikas.chaudh...@qlogic.com
Cc: jbottom...@parallels.com jbottom...@parallels.com, scsi
linux-scsi@vger.kernel.org, Lalit Chandivade
lalit.chandiv...@qlogic.com, Ravi Anand
From: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Vikas Chaudhary vikas.chaudh...@qlogic.com
---
include/scsi/iscsi_if.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/scsi/iscsi_if.h
From: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Vikas Chaudhary vikas.chaudh...@qlogic.com
---
drivers/scsi/qla4xxx/ql4_def.h | 3 ---
drivers/scsi/qla4xxx/ql4_os.c | 26 ++
2
On Thu 07 Mar 2013 12:23:13 CET, Jan Vesely wrote:
On Thu 21 Feb 2013 09:30:26 CET, Jan Vesely wrote:
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their
buffers
to potentially require exactly max
On Mon, Mar 25 2013, Jan Vesely wrote:
On Thu 07 Mar 2013 12:23:13 CET, Jan Vesely wrote:
On Thu 21 Feb 2013 09:30:26 CET, Jan Vesely wrote:
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their
v2: changed a comment
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their buffers
to potentially require exactly max segments and multiple pages in the last
segment. This patch modifies the check to allow
On Mon, Mar 25 2013, Jan Vesely wrote:
v2: changed a comment
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their buffers
to potentially require exactly max segments and multiple pages in the last
Il 25/03/2013 08:25, Bart Van Assche ha scritto:
+queue_num = smp_processor_id();
+while (unlikely(queue_num = vscsi-num_queues))
+queue_num -= vscsi-num_queues;
+
+tgt-req_vq = vq = vscsi-req_vqs[queue_num];
+}
+
+
On Mon 25 Mar 2013 15:24:57 CET, Jens Axboe wrote:
On Mon, Mar 25 2013, Jan Vesely wrote:
v2: changed a comment
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their
buffers
to potentially require
Hello there, I have a server in our test lab (specs below) that
doesn't appear to be getting nearly the write speeds that I was
expecting (test details below). In top terminology, there is one
CPU core at about 30% SI and each core shows anywhere from 1 to 15 %
SY and about the same for WA.
My
On Mon, Mar 25 2013, Jan Vesely wrote:
51506edc5741209311913
On Mon 25 Mar 2013 15:24:57 CET, Jens Axboe wrote:
On Mon, Mar 25 2013, Jan Vesely wrote:
v2: changed a comment
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However,
This series fixes a few critical issues with FCoE in 3.9.
1) bnx2fc had incorrect scsi host linkage in sysfs which prevents fcoemon
(fcoe userspace daemon) from interacting with it correctly.
2) 3 patches fix VN2VN mode configuration with new FCoE control interfaces.
3) Fixed lockdep warning
We can deadlock (s_active and fcoe_config_mutex) if a
port is being destroyed at the same time one is being created.
[ 4200.503113] ==
[ 4200.503114] [ INFO: possible circular locking dependency detected ]
[ 4200.503116] 3.8.0-rc5+ #8 Not
The fcoemon userspace daemon is searching for the a hostX
under the the /sys/bus/fcoe/devices/ctlrX/ entries. When
interfaces created using fcoe_sysfs and fcoe.ko this linkage
is setup correctly, but bnx2fc is not doing the same thing
and therefore fcoemon does not create the fcoe interface
for
Currently libfcoe is doing some libfc discovery layer initialization outside of
libfc. This patch moves this code into libfc and sets up a split in discovery
(one time) initialization code and (re-configurable) settings that will come in
the next patch.
Signed-off-by: Robert Love
Split discovery initialization in code that is setup once (fcoe_disc_init)
and code that can be re-configured (fcoe_disc_config).
Signed-off-by: Robert Love robert.w.l...@intel.com
Tested-by: Jack Morgan jack.mor...@intel.com
Reviewed-by: Bhanu Prakash Gollapudi bprak...@broadcom.com
---
The libfc discovery layer is being initialized in the
'create' paths for both legacy libfcoe module parameters
and fcoe_sysfs control interfaces. The problem is that
for VN2VN mode the discovery layer is initialized as if
it were in 'fabric' mode and it is not re-configured when
the mode is
The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
Linux 3.9-rc4 (2013-03-23 16:52:44 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git
tags/for-3.9-rc
for you to fetch changes up to
Patches 1 - 3 look ok to me.
Reviewed-by: Mike Christie micha...@cs.wisc.edu
On 03/25/2013 07:08 AM, vikas.chaudh...@qlogic.com wrote:
From: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Adheer Chandravanshi adheer.chandravan...@qlogic.com
Signed-off-by: Vikas
27 matches
Mail list logo
