Geschäftsvorschlag!!!

-- Geschäftsvorschlag!!! Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First National Bank von Süd Afrika) wo ich arbeite, auf einem Konto gestoßen,was nicht in anspruch genommen worden ist, wo

Re: Device or HBA level QD throttling creates randomness in sequetial workload

On Fri, Oct 21, 2016 at 05:43:35PM +0530, Kashyap Desai wrote: > Hi - > > I found below conversation and it is on the same line as I wanted some > input from mailing list. > > http://marc.info/?l=linux-kernel=147569860526197=2 > > I can do testing on any WIP item as Omar mentioned in above

[PATCH 1/1] libfc: don't have fc_exch_find log errors on a new exchange

With the error message I added in "libfc: sanity check cpu number extracted from xid" I didn't account for the fact that fc_exch_find is called with FC_XID_UNKNOWN at the start of a new exchange if we are the responder. It doesn't come up with the initiator much, but that's basically every

[PATCH] qla2xxx: Fix scsi scan hang triggered if adapter fails during init

A system can get hung task timeouts if a qlogic board fails during initialization (if the board breaks again or fails the init). The hang involves the scsi scan. In a nutshell, since commit beb9e315e6e0 ("qla2xxx: Prevent removal and board_disable race"): ...it is possible to have freed ha

Re: [PATCH] sd: fix uninitialized variable access in error handling

On Fri, Oct 21, 2016 at 10:32 AM, Arnd Bergmann wrote: > If sd_zbc_report_zones fails, the check for 'zone_blocks == 0' > later in the function accesses uninitialized data: > > drivers/scsi/sd_zbc.c: In function ‘sd_zbc_read_zones’: > drivers/scsi/sd_zbc.c:520:7: error:

[GIT PULL] SCSI fixes for 4.9-rc1

Five small fixes. Some of these, like the nested spinlock overwriting saved flags and the Kasan use after free look serious, but they seem not to have been picked up in testing or seen in the field. The biggest user visible issue is probably the wrong device handler for Clariion, which means

Re: [PATCH v3 4/8] megaraid_sas: Send SYNCHRONIZE_CACHE for non-raid to firmware

On 21.10.2016 15:33, Kashyap Desai wrote: > Commit- " 02b01e0 [SCSI] megaraid_sas: return sync cache call with success" > added the code in driver to return SYNCHRONIZE_CACHE without sending it to > firmware back in 2007. Earlier MR was mainly for Virtual Disk, > so same code continue for JBOD as

Re: [PATCH v2 4/7] megaraid_sas: Send SYNCHRONIZE_CACHE command to firmware

On 21.10.2016 13:01, James Bottomley wrote: > On Thu, 2016-10-20 at 02:05 -0700, Sumit Saxena wrote: >> From previous patch we have below changes in v2 - >> 1. Updated change log. Provided more detail in change log. >> 2. Agreed to remove module parameter. If we remove module parameter, >> we

Re: [PATCH v3 5/8] megaraid_sas: Send SYNCHRONIZE_CACHE for VD to firmware

On 21.10.2016 15:33, Kashyap Desai wrote: > From previous patch we have below changes in v2 (only for Virtual Disk)- > 1. Updated change log. Provided more detail in change log. > 2. Agreed to remove module parameter. If we remove module parameter, we > can ask customer to disable WCE on

[PATCH] sd: fix uninitialized variable access in error handling

If sd_zbc_report_zones fails, the check for 'zone_blocks == 0' later in the function accesses uninitialized data: drivers/scsi/sd_zbc.c: In function ‘sd_zbc_read_zones’: drivers/scsi/sd_zbc.c:520:7: error: ‘zone_blocks’ may be used uninitialized in this function [-Werror=maybe-uninitialized]

[PATCH v3 7/8] megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path for FW which does not support JBOD sequence map

CC: sta...@vger.kernel.org Signed-off-by: Sumit Saxena Reviewed-by: Hannes Reinecke Reviewed-by: Tomas Henzl --- drivers/scsi/megaraid/megaraid_sas_fusion.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 6/8] MAINTAINERS: Update megaraid maintainers list

Update MEGARAID drivers maintainers list. Signed-off-by: Sumit Saxena Reviewed-by: Hannes Reinecke --- MAINTAINERS | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index f0ee7a6..8b9117f 100644

[PATCH v3 8/8] megaraid_sas: driver version upgrade

Signed-off-by: Sumit Saxena --- drivers/scsi/megaraid/megaraid_sas.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/megaraid/megaraid_sas.h b/drivers/scsi/megaraid/megaraid_sas.h index 43fd14f..74c7b44 100644 ---

[PATCH v3 1/8] megaraid_sas: For SRIOV enabled firmware, ensure VF driver waits for 30secs before reset

For SRIOV enabled firmware, if there is a OCR(online controller reset) possibility driver set the convert flag to 1, which is not happening if there are outstanding commands even after 180 seconds. As driver does not set convert flag to 1 and still making the OCR to run, VF(Virtual function)

[PATCH v3 4/8] megaraid_sas: Send SYNCHRONIZE_CACHE for non-raid to firmware

Commit- " 02b01e0 [SCSI] megaraid_sas: return sync cache call with success" added the code in driver to return SYNCHRONIZE_CACHE without sending it to firmware back in 2007. Earlier MR was mainly for Virtual Disk, so same code continue for JBOD as well whenever JBOD support was added and it

[PATCH v3 3/8] megaraid_sas: Do not fire DCMDs during PCI shutdown/detach

This patch addresses the issue of driver firing DCMDs in PCI shutdown/detach path irrespective of firmware state. Driver will check for whether firmware is operational state or not before firing DCMDs. If firmware is in unrecoverbale state or does not become operational within specfied time,

[PATCH v3 5/8] megaraid_sas: Send SYNCHRONIZE_CACHE for VD to firmware

>From previous patch we have below changes in v2 (only for Virtual Disk)- 1. Updated change log. Provided more detail in change log. 2. Agreed to remove module parameter. If we remove module parameter, we can ask customer to disable WCE on drive to get similar impact. 3. Always Send

[PATCH v3 2/8] megaraid_sas: Send correct PhysArm to FW for R1 VD downgrade

This patch fixes the issue of wrong PhysArm was sent to firmware for R1 VD downgrade. Signed-off-by: Kiran Kumar Kasturi Signed-off-by: Sumit Saxena Reviewed-by: Hannes Reinecke Reviewed-by: Tomas Henzl

[PATCH v3 0/7] megaraid_sas: Updates for scsi-next

Changes in v3 two logical patches created for "Send SYNCHRONIZE_CACHE command to firmware" - Send SYNCHRONIZE_CACHE for JBOD to firmware - Send SYNCHRONIZE_CACHE for VD to firmware Changes in v2: 1. Removed unconditional msleep and moved calls to atomic_read into

Re: [PATCH v2 4/7] megaraid_sas: Send SYNCHRONIZE_CACHE command to firmware

On Fri, 2016-10-21 at 17:38 +0530, Kashyap Desai wrote: > > -Original Message- > > From: James Bottomley [mailto:j...@linux.vnet.ibm.com] > > Sent: Friday, October 21, 2016 4:32 PM > > To: Sumit Saxena; linux-scsi@vger.kernel.org > > Cc: martin.peter...@oracle.com; the...@redhat.com; > >

RE: Device or HBA level QD throttling creates randomness in sequetial workload

Hi - I found below conversation and it is on the same line as I wanted some input from mailing list. http://marc.info/?l=linux-kernel=147569860526197=2 I can do testing on any WIP item as Omar mentioned in above discussion. https://github.com/osandov/linux/tree/blk-mq-iosched Is there any

RE: [PATCH v2 4/7] megaraid_sas: Send SYNCHRONIZE_CACHE command to firmware

> -Original Message- > From: James Bottomley [mailto:j...@linux.vnet.ibm.com] > Sent: Friday, October 21, 2016 4:32 PM > To: Sumit Saxena; linux-scsi@vger.kernel.org > Cc: martin.peter...@oracle.com; the...@redhat.com; > kashyap.de...@broadcom.com; sta...@vger.kernel.org > Subject: Re:

Re: [PATCH v2 4/7] megaraid_sas: Send SYNCHRONIZE_CACHE command to firmware

On Thu, 2016-10-20 at 02:05 -0700, Sumit Saxena wrote: > From previous patch we have below changes in v2 - > 1. Updated change log. Provided more detail in change log. > 2. Agreed to remove module parameter. If we remove module parameter, > we > can ask customer to disable WCE on drive to

Re: [PATCH v2 4/7] megaraid_sas: Send SYNCHRONIZE_CACHE command to firmware

On 10/20/2016 05:05 AM, Sumit Saxena wrote: From previous patch we have below changes in v2 - 1. Updated change log. Provided more detail in change log. 2. Agreed to remove module parameter. If we remove module parameter, we can ask customer to disable WCE on drive to get similar

[PATCH] scsi: ufs: changing authors e-mail

Although I am leaving Synopsys, I would like to keep working with the linux kernel community and help in what you might find useful. For that I am sending this patch to change my contact e-mail. Signed-off-by: Joao Pinto --- drivers/scsi/ufs/tc-dwc-g210-pci.c| 4 ++--

Re: [PATCH 2/6] target: fix potential race window in target_sess_cmd_list_waiting()

On Mon, 2016-08-22 at 10:54 +0200, Hannes Reinecke wrote: > target_sess_cmd_list_waiting() might hit on a condition where > the kref for the command is already 0, but the destructor has > not been called yet (or is stuck in waiting for a spin lock). > Rather than leaving the command on the list we

Re: [PATCH 1/6] target: fix hang in target_wait_for_sess_cmds()

On Mon, 2016-08-22 at 10:54 +0200, Hannes Reinecke wrote: > When shutting down a session I'm seeing this hung_task message: > > INFO: task kworker/u128:0:6 blocked for more than 480 seconds. > Tainted: GE N 4.4.17-default+ #241 > "echo 0 >

Re: [PATCH 0/6] tcm_fc fixes

Hi Hannes & Martin, Apologies for the extended delay on this. Comments below. On Mon, 2016-08-22 at 10:54 +0200, Hannes Reinecke wrote: > Hi Nic, > > here's a set of patches and fixes I've found during debugging > FCoE over virtio. > The first two fix a race condition I've encountered during