From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:11816 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752693AbdFSPrt (ORCPT ); Mon, 19 Jun 2017 11:47:49 -0400 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3589881F01 for ; Mon, 19 Jun 2017 15:47:39 +0000 (UTC) Date: Mon, 19 Jun 2017 11:47:35 -0400 From: Mike Snitzer To: Ondrej Kozina Cc: linux-block@vger.kernel.org, dm-devel@redhat.com, mpatocka@redhat.com, mbroz@redhat.com Subject: Re: dm integrity tests crash kernel (4.12-rc5) Message-ID: <20170619154735.GA16472@redhat.com> References: <2b97933e-3f94-8510-cefd-13fae445400e@redhat.com> <20170619142026.GA92582@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org On Mon, Jun 19 2017 at 11:16am -0400, Ondrej Kozina wrote: > On 06/19/2017 04:20 PM, Mike Snitzer wrote: > > > >Looks like submit_flush_bio() is disabling/enabling interrupts from > >interrupt context. Ondrej, does this patch fix the issue? > > I let it spin for 30 minutes on patched dm-integrity and everything > seems ok now. The moment I loaded back the old one it fell on face > almost immediately again. OK, I'll get it staged as a fix for 4.12. Thanks, Mike