Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp73438pxb; Tue, 2 Mar 2021 19:40:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJzrfvyWJyBOAtXTrCzNAX1w0ZSVrH4gApSmb/Po0GBp8rRsIf6Mnn1vWG/N4IE6lEVbPT2V X-Received: by 2002:aa7:d2d5:: with SMTP id k21mr17550541edr.216.1614742802273; Tue, 02 Mar 2021 19:40:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614742802; cv=none; d=google.com; s=arc-20160816; b=nYykERlhl7hGdNDze70d1HebGFbbjBsn4Wq9Y1T6PAvaVaJRuPd8B3qJ89zqW1MzHc EOiOba+yFazC+/eMAeW2HwS9WZkLb9ikM4934ZV0Sp9+68JjHJo4Cp2AngXl1eroAJuo y3wU1aS4EawqD1rpBw6Eok/4P2C2KcW1iC+1w4LP1pLz03tmc+hXGgX42c8LUJgJapr1 ImV2X+mBFVEYJ007gMC/diJemjM5V3wmfKZj6D+acj3dxKUwp43hYl691NW2PqVG5aUn UGXLc6xE5gtNWdSwhWbaizFRJ5lOIueLpEud9vOmV3UjUO8uBYwsDcDAPyoO/8BAbGFn nf4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=DUPs1KEV4Av+7UUrefUoRIbPHAt6FDitpk8f8zWqVeM=; b=Cyp6L5lklhzgOoXLCyzEawqVWs1J3+BV9ViKpjd26sIPKWvCnRGnq0ENUf1HmktN77 Gx7HSKXe8p8ScADSS2fV1by8HgtJJXixWMt9TJ3DcLrrZTopMwNUBZG26EROJFhzSYi3 4bR2emmeJn1yC1bTnAYabJVQp1IqLc2w4xxSbAaokWVL1OgPbAjSrsmZIzzAwDrIaWVD oqPrmKOREGJGIoaWVNE7Zw6ndqE3cL3NtwSPCRshn8cH/r8zArBrnaUEIIJ8s8vYUFXi cKBeTlIOOwazPEBGnRrP9ov8Eq45B/Smi7DgazdO6BsEUUVXiAA1h7Ac0h/uPjAbCRye 4e8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h14si14166038ejt.198.2021.03.02.19.39.39; Tue, 02 Mar 2021 19:40:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235998AbhCAN42 (ORCPT + 99 others); Mon, 1 Mar 2021 08:56:28 -0500 Received: from mx2.suse.de ([195.135.220.15]:50826 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235974AbhCAN4M (ORCPT ); Mon, 1 Mar 2021 08:56:12 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 4EA45AC24; Mon, 1 Mar 2021 13:55:31 +0000 (UTC) Subject: Re: [PATCH] nvme-tcp: Check if request has started before processing it To: Daniel Wagner , Keith Busch Cc: Sagi Grimberg , Jens Axboe , Christoph Hellwig , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org References: <20210212210929.GA3851@redsun51.ssa.fujisawa.hgst.com> <73e4914e-f867-c899-954d-4b61ae2b4c33@suse.de> <20210215104020.yyithlo2hkxqvguj@beryllium.lan> <20210226123534.4oovbzk4wrnfjp64@beryllium.lan> <9e209b12-3771-cdca-2c9d-50451061bd2a@suse.de> <20210226161355.GG31593@redsun51.ssa.fujisawa.hgst.com> <20210226171901.GA3949@redsun51.ssa.fujisawa.hgst.com> <20210301132639.n3eowtvkms2n5mog@beryllium.lan> From: Hannes Reinecke Message-ID: <786dcef5-148d-ff34-590c-804b331ac519@suse.de> Date: Mon, 1 Mar 2021 14:55:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <20210301132639.n3eowtvkms2n5mog@beryllium.lan> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/1/21 2:26 PM, Daniel Wagner wrote: > On Sat, Feb 27, 2021 at 02:19:01AM +0900, Keith Busch wrote: >> Crashing is bad, silent data corruption is worse. Is there truly no >> defense against that? If not, why should anyone rely on this? > > If we receive an response for which we don't have a started request, we > know that something is wrong. Couldn't we in just reset the connection > in this case? We don't have to pretend nothing has happened and > continuing normally. This would avoid a host crash and would not create > (more) data corruption. Or I am just too naive? > This is actually a sensible solution. Please send a patch for that. Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer