From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurence Oberman Subject: Re: dm-mq and end_clone_request() Date: Fri, 5 Aug 2016 07:43:30 -0400 (EDT) Message-ID: <1931660518.8323360.1470397410683.JavaMail.zimbra@redhat.com> References: <20160801175948.GA6685@redhat.com> <1a460c29-1530-d3e1-25ba-736d86aff12e@sandisk.com> <20160803004013.GA19956@redhat.com> <20160804161047.GC6989@redhat.com> <4d60017e-818c-5630-549e-bf280abcf1c3@sandisk.com> <20160804235850.GB13132@redhat.com> <1649218.8261013.1470359248073.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mx6-phx2.redhat.com ([209.132.183.39]:40947 "EHLO mx6-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934967AbcHELng (ORCPT ); Fri, 5 Aug 2016 07:43:36 -0400 In-Reply-To: <1649218.8261013.1470359248073.JavaMail.zimbra@redhat.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Mike Snitzer Cc: Bart Van Assche , dm-devel@redhat.com, linux-scsi@vger.kernel.org ----- Original Message ----- > From: "Laurence Oberman" > To: "Mike Snitzer" > Cc: "Bart Van Assche" , dm-devel@redhat.com, linux-scsi@vger.kernel.org > Sent: Thursday, August 4, 2016 9:07:28 PM > Subject: Re: dm-mq and end_clone_request() > > > > ----- Original Message ----- > > From: "Mike Snitzer" > > To: "Bart Van Assche" > > Cc: dm-devel@redhat.com, "Laurence Oberman" , > > linux-scsi@vger.kernel.org > > Sent: Thursday, August 4, 2016 7:58:50 PM > > Subject: Re: dm-mq and end_clone_request() > > > > I've staged another fix, Laurence is seeing success with this added: > > https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.8&id=d50a6450104c237db1dc75314d17b78c990a8c05 > > > > I'll be sending all the fixes I've queued to Linus tonight or early > > tomorrow (since I'll then be on vacation until Monday 8/15). > > > Hello Bart, > > I applied that patch to your kernel and while I still obviously see all the > debug logging its no longer failing fio for me. > I ran 8 loops with 20 parallel fio runs. This was on a different server to > the one I had been testing on. > > However I am concerned about timing playing a part here here so let us know > what you find. > > Thanks > Laurence Replying to my own message: Hi Bart, Mike Further testing has shown we are still exposed here so more investigation is necessary. The above patch seems to help but I still see sporadic cases of errors escaping up the stack. I expect you will see the same so more work to do here to figure this out. Thanks Laurence