Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1788554imm; Thu, 19 Jul 2018 07:55:19 -0700 (PDT) X-Google-Smtp-Source: AAOMgpch/KEF+xwTPyH7Bvh466ClX7UYic7EaBQfv/1CfLVG+lk6s4HDkmfXmp9PCE0u+ZDA+jkw X-Received: by 2002:a62:d24a:: with SMTP id c71-v6mr9902509pfg.242.1532012119682; Thu, 19 Jul 2018 07:55:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532012119; cv=none; d=google.com; s=arc-20160816; b=Al6q4vulbtoPNxeTEwClDyg9fcUxRy/qD+v4oO0B2NaRdVlXAKb7P9EQedgJ75eqRA kGgVCgYPIQYVsIhvkQARa6GdaLzhQYYLs1IwFUuMTLmIPY4qE0aOQdHc+3xhTkJAR3no LpUfRz6KBYOrksKPbOPa35RFeSIuiuunujbSqCVu/hXxfzRR3+QNGI/8pd0crh50SCrI 2u0+tdHL7agpA9Wk/ebB0yD4NmOXq/Dte7GNO5ACaBjHP2rw0tN/VuhzmBBORiESjN1f ohvUTIQHxqk90xoWf4PE9sGuuYlMZ63vBCMQwK+eBjGqhknL9n6NCPtMK5WsbSFe7rb4 MoAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=RXpDuamYOgSZB9VUXbhg/uBbkCGVln6ts68hxDJpKuE=; b=q9m8JWldR1/8yvAVgpE+VjT60N42kmfE06liqlpqXabJcvp6voe6rGr8nS7pmjGB0j /HhdLtsEf8I0KSuzIXqFnb3UJ2slY11+H5i6LHxzgtIf78f5wUmWwMDu1hJwht7/Kjst rPTkm5dIZxqMmjaTettuetpaXFLu1gRoJUEVYQxMQhDRjCzWMHUSdBcp9OjU67IiN7nY Z3Jp/xqN3pMWLWGiLpHzjvfJbWMFmF6bCgesrsuLpKWEcQrWTpvK3jKZzTErkU21QpjS k4n47Z5yoVnZRAJWDDYlbxnWczoQ0G67U6AuyG41Gxyw70H4KRJJbxE0Jy0wrmYTlFle yNTg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f8-v6si6088815plb.381.2018.07.19.07.55.04; Thu, 19 Jul 2018 07:55:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731813AbeGSPh7 (ORCPT + 99 others); Thu, 19 Jul 2018 11:37:59 -0400 Received: from mx2.suse.de ([195.135.220.15]:42958 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730521AbeGSPh7 (ORCPT ); Thu, 19 Jul 2018 11:37:59 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 7FAFAAE7E; Thu, 19 Jul 2018 14:54:25 +0000 (UTC) Date: Thu, 19 Jul 2018 16:54:22 +0200 From: Johannes Thumshirn To: Christoph Hellwig Cc: Sagi Grimberg , Keith Busch , James Smart , Hannes Reinecke , Ewan Milne , Max Gurtovoy , Linux NVMe Mailinglist , Linux Kernel Mailinglist Subject: Re: [PATCH 0/4] Rework NVMe abort handling Message-ID: <20180719145422.2tdrbwa34gheuam3@linux-x5ow.site> References: <20180719132838.15556-1-jthumshirn@suse.de> <20180719134203.GA15212@lst.de> <20180719141025.yveza2svhvc2r4lw@linux-x5ow.site> <20180719142355.GA18800@lst.de> <20180719143534.i36vo45lhz24xbrg@linux-x5ow.site> <20180719145005.GA21000@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180719145005.GA21000@lst.de> User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 19, 2018 at 04:50:05PM +0200, Christoph Hellwig wrote: > The upper layer is only going to retry after tearing down the transport > connection. And a tear down of the connection MUST clear all pending > commands on the way. If it doesn't we are in deep, deep trouble. > > A NVMe abort has no chance of clearing things at the transport layer. OK so all I can do in my case (if I want soft error recovery) is send out a transport abort in the timeout handler and then rearm the timer and requeue the command. Which leaves us to the FC patch only, modified of cause. -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton HRB 21284 (AG N?rnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850