From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mauricio Faria de Oliveira Subject: Re: block: don't check request size in blk_cloned_rq_check_limits() Date: Thu, 16 Jun 2016 09:35:47 -0300 Message-ID: <57629D23.1090704@linux.vnet.ibm.com> References: <1464593093-93527-1-git-send-email-hare@suse.de> <20160610131901.GA28570@redhat.com> <575BE182.5010304@suse.de> <575C0DAE.7070502@suse.de> <5760F6BC.60109@suse.de> <576127FC.9020608@kernel.dk> <57612F12.5070505@suse.de> <5761838E.1000106@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:56530 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754450AbcFPMgA (ORCPT ); Thu, 16 Jun 2016 08:36:00 -0400 Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u5GCY7Gg038999 for ; Thu, 16 Jun 2016 08:35:59 -0400 Received: from e24smtp04.br.ibm.com (e24smtp04.br.ibm.com [32.104.18.25]) by mx0a-001b2d01.pphosted.com with ESMTP id 23kpn0dayc-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Thu, 16 Jun 2016 08:35:58 -0400 Received: from localhost by e24smtp04.br.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 16 Jun 2016 09:35:56 -0300 In-Reply-To: <5761838E.1000106@linux.vnet.ibm.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Brian King , Hannes Reinecke , Jens Axboe , "Martin K. Petersen" Cc: Mike Snitzer , Brian King , linux-scsi@vger.kernel.org, linux-block@vger.kernel.org, mark.bergman@uphs.upenn.edu Hey, On 06/15/2016 01:34 PM, Brian King wrote: > Mauricio was looking at this, adding him to cc. We did have a KVM config > where we could reproduce this issue as well, I think with some PCI passthrough > adapters. Mauricio - do you have any more details about the KVM config that > reproduced this issue and did you ever try to reproduce this with an upstream > kernel? It's KVM guest w/ SLES 12 SP1 + kernel updates (3.12.53-60.30 introduced the error) and PCI passthrough of Emulex FC and FCoE adapters, connected to 4 storage systems (DS8000, XIV, SVC, and FlashSystem 840). It seems only the XIV LUNs never hit the problem, but it didn't seem to be storage-specific, as FS840 LUNs had a mix of hit/not-hit the problem. One thing is that all paths of a LUN were either failed or not - no mix within a LUN. Unfortunately not too much analysis was performed on this system at the time -- Hannes had already made good progress w/ the customer, and some test kernel builds that resolved the issue were made available soon. Now that the topic is under discussion, I've asked for some time slots on that system, so we can test an upstream kernel and try to reproduce the problem and analyze it more closely. -- Mauricio Faria de Oliveira IBM Linux Technology Center