Received: by 2002:a05:7412:2a8c:b0:e2:908c:2ebd with SMTP id u12csp2466075rdh; Wed, 27 Sep 2023 03:39:19 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEzKKI62NtIyKP9861JHDc4D4o9seZlRCN+gvj56tdH9LCjgeuCzZXzx0xGJNUZkH6idfzs X-Received: by 2002:a05:6358:98a3:b0:145:6b8f:a0de with SMTP id q35-20020a05635898a300b001456b8fa0demr2168514rwa.16.1695811159514; Wed, 27 Sep 2023 03:39:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695811159; cv=none; d=google.com; s=arc-20160816; b=i5xtnk9Ia+ANJUEehuHYr21x3nToWc6R5dUp9T86gqiDGfH3GBML+2ZuVtbD1hCLm8 zd7w27hyqKE6gQrlJ5kEUT/b2NY9Jy2ugHSJkiSv1n0p/6kY8Jy4Lgf8peoNxuOL+vax 7QRZ9i0x1NW/smS7a02MJqYaiFpN5yybcMlYtt1o9+/9nhLsNqlgFfEPkBOQhkw/KmY0 QO6GbTGn7iadDgx+hdppJ0P3/xwPHLsosZdJuRRrcRLmbSut1qIPKF0+CiK0rI8z2k8a ageaUrFP1w3PON+YUTL74Mv7amCQUyI9oXvz7YM6vEyKyykyph2whxd0XK4EZu/Q6d5s jqbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=IO3jAfRcuG3K3Qn8vVKgEmzrEP9fPPND2QZfx5Rmgdw=; fh=WIS7y17ytUE3qzcQCxU7EGiJX4lC0/KyFx08l4uage4=; b=tqhf46vsimPYDK2HuWpN/Cyf30Mq+BwUqYx4h7zC8PK5jv/Idfj1Dfryg//wKzVbII 53Chf1KuuEo6YI/MEaM1SRgiJdZ3icX4UMcWVxEw1GIXxU38772GJGEgyHML3aCPq3sw FzGVlFrpzPkaH+MeUM+2LChQpZzmZ+EdhQ3TZmDXmBM8ZF6t10Yctz0NmgbV11DLzjTi OoSr7IBTb1ivCqxLzPx7oy/70X5GdTP8KubLlSn5XknYbE/KCLTGoAookJ1uP26NdonG 7VWYGWzhEpbh57BnamZ0JtYAFVa3d3/Ppg8elzm58Oe/Pk5pFUWSYTJWr5Hr/s59J8f5 yysw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from morse.vger.email (morse.vger.email. [23.128.96.31]) by mx.google.com with ESMTPS id l191-20020a6391c8000000b0057047d68821si14822599pge.565.2023.09.27.03.39.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Sep 2023 03:39:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by morse.vger.email (Postfix) with ESMTP id 57BA280B822F; Wed, 27 Sep 2023 02:42:03 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at morse.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230440AbjI0Jlz (ORCPT + 99 others); Wed, 27 Sep 2023 05:41:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45878 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231281AbjI0Jlt (ORCPT ); Wed, 27 Sep 2023 05:41:49 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C98ADC0; Wed, 27 Sep 2023 02:41:47 -0700 (PDT) Received: from kwepemm000012.china.huawei.com (unknown [172.30.72.57]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4RwWm21jq5zrTBX; Wed, 27 Sep 2023 17:39:30 +0800 (CST) Received: from [10.174.178.220] (10.174.178.220) by kwepemm000012.china.huawei.com (7.193.23.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 27 Sep 2023 17:41:45 +0800 Message-ID: <98ea6e9b-cbfb-0485-6452-e3d979aaed54@huawei.com> Date: Wed, 27 Sep 2023 17:41:44 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [RFC PATCH v2 00/18] scsi: scsi_error: Introduce new error handle mechanism Content-Language: en-US To: Hannes Reinecke , Mike Christie , Christoph Hellwig CC: "James E . J . Bottomley" , "Martin K . Petersen" , , , , References: <20230901094127.2010873-1-haowenchao2@huawei.com> <47bed3cb-f307-ec55-5c28-051687dab1ea@huawei.com> <06268327-cfed-f266-34a7-fda69411ef2a@huawei.com> From: Wenchao Hao In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.178.220] X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To kwepemm000012.china.huawei.com (7.193.23.142) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.2 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on morse.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (morse.vger.email [0.0.0.0]); Wed, 27 Sep 2023 02:42:03 -0700 (PDT) On 2023/9/27 15:59, Hannes Reinecke wrote: > On 9/26/23 14:57, Wenchao Hao wrote: >> On 2023/9/26 1:54, Mike Christie wrote: >>> On 9/25/23 10:07 AM, Wenchao Hao wrote: >>>> On 2023/9/25 22:55, Christoph Hellwig wrote: >>>>> Before we add another new error handling mechanism we need to fix the >>>>> old one first.  Hannes' work on not passing the scsi_cmnd to the various >>>>> reset handlers hasn't made a lot of progress in the last five years and >>>>> we'll need to urgently fix that first before adding even more >>>>> complexity. >>>>> >>>> I observed Hannes's patches posted about one year ago, it has not been >>>> applied yet. I don't know if he is still working on it. >>>> >>>> My patches do not depend much on that work, I think the conflict can be >>>> solved fast between two changes. >>> >>> I think we want to figure out Hannes's patches first. >>> >>> For a new EH design we will want to be able to do multiple TMFs in parallel >>> on the same host/target right? >>> >> >> It's not necessary to do multiple TMFs in parallel, it's ok to make sure >> each TMFs do not affect each other. >> >> For example, we have two devices: 0:0:0:0 and 0:0:0:1 >> >> Both of them request device reset, they do not happened in parallel, but >> would in serial. If 0:0:0:0 is performing device reset in progress, 0:0:0:1 >> just wait 0:0:0:0 to finish. >> > Well, not quite. Any higher-order TMFs are serialized by virtue of SCSI-EH, but command aborts (which also devolve down to TMFs on certain drivers) do run in parallel, and there we will be requiring multiple TMFs. > It's best that multiple TMFs can run in parallel, again, looking forwarding to your changes. > Cheers, > > Hannes