Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp4226848imm; Mon, 25 Jun 2018 11:52:21 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI2fhOEUZmlhQDzy4VSdaCu3qYm7mVxr0JRh+2loQtAv5uc2YgxWYX5TyZoQadcjPX7Fkl8 X-Received: by 2002:a63:a347:: with SMTP id v7-v6mr11413692pgn.182.1529952741494; Mon, 25 Jun 2018 11:52:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529952741; cv=none; d=google.com; s=arc-20160816; b=iqFaOgSEOmr5H34diyPQPu6voWVhbLrNHYUSP2Ekw4RKvRuWkUmkwYCWKrTUUQlY8L jgd+dPr+m91paa6BsDQhbfipyrQUscGvS6K9n8wlOd6wBYbcwXHOkHVdjBXTRo56pKSe Falo/sDHHxvIZ6IWSYCBMn23Vww9rEI+vX9CrzehKAgKygLZsYqY5FxMUBuCnI7591UT AezFfEAvm+3HZnubvOpUrG6SDa34m3Ie9Fr966bFt+MRk/dY7BtCrDu1qng0P2HF9n/f Oq3y9MHJ1Q07QPJZRtrpajI+XQAMbY+ORksRKKLaM5lEtEnYMcE8i2jPsX3ObWdXo830 5CyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=ai3UErSE2HrtLR5xlIQP7TxlrXVVqmedYvwFLqB3lX4=; b=tlVxyad9FCgoKRfMJB8AqZlOoUOxr532gwffH4SPoA8wUIKkxBbOnvcPFWu0J1vGVt FDdzTbE+hxne+QLVpij1ZdKr0zLYK3vySHLpz8c7n7L1MEONAlryZnETr4l585ZaEdlZ Nyr8akRRrZNoVvNOB77MGXIy7hB1SQp3ZZsDaufZeyIRp/y7mOyeUAoxTbnguRpdL2MI XTCUACXaAi8tEmelXlZozZzmaZLOMVefVM5O+B6ofVYU7GimbpMFUkrVpu1FQWqvx3XO fFM94yrIHuskQOaxh0Bcd/k53EEtnnttPwnKNfIXScWXU7CxINVVdPcbvao43+HCuSUr dhSQ== 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 x11-v6si9785996pgx.118.2018.06.25.11.52.05; Mon, 25 Jun 2018 11:52:21 -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 S965067AbeFYSvO (ORCPT + 99 others); Mon, 25 Jun 2018 14:51:14 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:34416 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964944AbeFYSvM (ORCPT ); Mon, 25 Jun 2018 14:51:12 -0400 Received: by mail-wm0-f68.google.com with SMTP id l15-v6so13251367wmc.1; Mon, 25 Jun 2018 11:51:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ai3UErSE2HrtLR5xlIQP7TxlrXVVqmedYvwFLqB3lX4=; b=eCNXxAh8tvT6XRc5fFDld4vpJZjiUSW9zQoeQaqMLkqBZkWcguyQk4CDtzDvh0Ib7G wmCbCNQXr4f99S6oURX9WzUdSsMXVoQJry1hsrRJRyG4AJQJNkZKSKQj5IZOfYhQjtwu Kh72VeJm7a9z2m2n5igCaydzWCvCSbmeZWCyocaodPDrzhmUQQvVjdhFagp124XmJu7G MtIbvaaUixh8zbVQEj6NH9zBToxUkOPfTRtVsbCNUbc+5RNRHsWexJQfP72SKOwXuRxF /x0TdmeAXIf8KKIST/yKqU4oUdPGx0fcrgGrcHTIpV3t40uaIzoh6kFbodK5wm1Jr94g VYkA== X-Gm-Message-State: APt69E0Opxz2NKrXBr5BY8zV+zgyZ7msg5LcNsiE7mPL3TLSxTmhuUq9 KBv8GeSYRIhbNN2y1QBdD36yB3dL X-Received: by 2002:a1c:7141:: with SMTP id m62-v6mr1808772wmc.157.1529952670285; Mon, 25 Jun 2018 11:51:10 -0700 (PDT) Received: from [192.168.64.169] (bzq-219-42-90.isdn.bezeqint.net. [62.219.42.90]) by smtp.gmail.com with ESMTPSA id 14-v6sm921784wmh.8.2018.06.25.11.51.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jun 2018 11:51:09 -0700 (PDT) Subject: Re: [PATCH 5/5] nvme: use __blk_mq_complete_request in timeout path To: "jianchao.wang" , Christoph Hellwig Cc: axboe@kernel.dk, martin.petersen@oracle.com, keith.busch@intel.com, josef@toxicpanda.com, ulf.hansson@linaro.org, linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org References: <1529500964-28429-1-git-send-email-jianchao.w.wang@oracle.com> <1529500964-28429-6-git-send-email-jianchao.w.wang@oracle.com> <20180620143956.GA20950@lst.de> <42583ee2-fe9d-39da-b82a-38a27b03fdb3@oracle.com> <1817441e-6810-ed40-a8fd-403742818aae@grimberg.me> From: Sagi Grimberg Message-ID: <80d1be8f-859e-5feb-a53e-c8be9c3e0213@grimberg.me> Date: Mon, 25 Jun 2018 21:51:07 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> Given the amount of fixes (and fixes of fixes) we had in the timeout handler, maybe it'd be a good idea to step back and take a another look? >> >> Won't it be better to avoid disabling the device and return >> BLK_EH_RESET_TIMER if we are not aborting in the timeout handler? >> > > Yes, that would be an ideal status for nvme-pci. > But we have to depend on the timeout handler to handle the timed out request from nvme_reset_work. Yes, so if the timeout handler is invoked from the reset, it should simply set a proper failed status and return BLK_EH_DONE.