Re: block: remove artifical max_hw_sectors cap

2014-12-23 Thread Christoph Hellwig
On Mon, Dec 22, 2014 at 11:31:53AM +0100, Stefan Priebe - Profihost AG wrote: > Hi, > > since the below patch i've some problems with iscsi. > > The LIO based iscsi Server is full of messages like this: > SCSI OP 2ah with too big sectors 8344 exceeds fabric_max_sectors: 8192 > > And the client s

Re: Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap")

2014-12-23 Thread Christoph Hellwig
On Sun, Dec 21, 2014 at 02:44:20PM -0800, Kenneth R. Crudup wrote: > > I had issues with my Samsung 4GB disk recently in Linus' master tree kernels, > and have bisected it to the above commit. When doing running bonnie++ (etc. > I get EIOs. > > Some info is below, let me know if you need anything

Re: [Patch] Fix regression in 3.18 caused by e05fe29248 qla2xxx: Honor FCP_RSP retry delay timer field.

2014-12-23 Thread Christoph Hellwig
Chad, Saurav, does this look ok to you? -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[patch] mptfusion: buffer overflow in mptctl_do_mpt_command()

2014-12-23 Thread Dan Carpenter
The main problem is that this copy can overflow: if (copy_from_user(mf, mfPtr, karg.dataSgeOffset * 4)) { We try to prevent an overflow by checking "if (sz > ioc->req_sz) {" but the problem is that "sz" is signed so the test can underflow or their could be an integer overflow. A second p

[PATCH] constants.c: asc/ascq codes, sync to T10 20141221

2014-12-23 Thread Douglas Gilbert
The last time these SCSI asc/ascq codes were synced with T10 was 20130605. This patch is against lk 3.19.0-rc1 . ChangeLog: sync the SCSI ASC/ASCQ number to string tables with those found at http://www.t10.org/lists/asc-num.txt dated 20141221 Signed-off-by: Douglas Gilbert --- a/drivers/s

[PATCH] cleanup on stack DECLARE_COMPLETIONs

2014-12-23 Thread Nicholas Mc Guire
fixups for incorrect use of DECLARE_COMPLETION. see also commit 6e9a4738 ("completions: lockdep annotate on stack completions") The only somewhat special case being drivers/misc/sgi-gru/grukservices.c:quicktest2 which had a static qualifier in the original DECLARE_COMPLETION() but that seems to be

[PATCH] scsi: unnecessary double init_completion removed

2014-12-23 Thread Nicholas Mc Guire
The double call to init_completion(&ha->disable_acb_comp); looks like an editing mistake only - dropped. patch is against 3.18.0 linux-next scripts/get_maintainer.pl -f drivers/scsi/qla4xxx/ql4_os.c returned Vikas Chaudhary (supporter:QLOGIC QLA4XXX iS...) but that no longer seems to be a valid

Re: [PATCH] cleanup on stack DECLARE_COMPLETIONs

2014-12-23 Thread Felipe Balbi
On Tue, Dec 23, 2014 at 06:34:08PM +0100, Nicholas Mc Guire wrote: > fixups for incorrect use of DECLARE_COMPLETION. see also commit > 6e9a4738 ("completions: lockdep annotate on stack completions") > The only somewhat special case being > drivers/misc/sgi-gru/grukservices.c:quicktest2 > which had

[PATCH 1/1] IOMMU Fault occurs when IO and abort IO is out of order

2014-12-23 Thread Anil Chintalapati (achintal)
When I/O is aborted by mid-layer, fnic FW will complete the I/O before completing the abort task. In some cases abort request is completed before the I/O, which could lead to inconsistent driver and firmware states. In this case firmware reset would clear the inconsistent state Signed-off-by:

RE: [PATCH V2 1/4] be2iscsi : Fix the retry count for boot targets

2014-12-23 Thread Sony John-N
From: Mike Christie [micha...@cs.wisc.edu] Sent: Monday, December 22, 2014 3:54 PM To: Sony John-N; linux-scsi@vger.kernel.org Cc: Minh Duc Tran; Jayamohan Kallickal Subject: Re: [PATCH V2 1/4] be2iscsi : Fix the retry count for boot targets On 12/22/2014