From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F85FC433F5 for ; Mon, 10 Jan 2022 20:21:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343528AbiAJUVe (ORCPT ); Mon, 10 Jan 2022 15:21:34 -0500 Received: from frasgout.his.huawei.com ([185.176.79.56]:4386 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241448AbiAJUVd (ORCPT ); Mon, 10 Jan 2022 15:21:33 -0500 Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4JXlX70QDSz67DWp; Tue, 11 Jan 2022 04:18:47 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml738-chm.china.huawei.com (10.206.15.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Mon, 10 Jan 2022 21:21:30 +0100 Received: from [10.47.24.251] (10.47.24.251) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Mon, 10 Jan 2022 20:21:29 +0000 Subject: Re: [issue report] pm8001 issues (was driver crashes with IOMMU enabled) To: , , CC: , , , , , References: <894f766f-74b7-62b1-f6d2-82ac85b6478f@huawei.com> <00505633-c8c0-8213-8909-482bf43661cd@huawei.com> <1cc92b2d-3670-7843-d68a-06fe68521d24@huawei.com> <0cc0c435-b4f2-9c76-258d-865ba50a29dd@huawei.com> From: John Garry Message-ID: <34319d65-104d-55a0-175d-96cf3f0aea89@huawei.com> Date: Mon, 10 Jan 2022 20:21:13 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.24.251] X-ClientProxiedBy: lhreml743-chm.china.huawei.com (10.201.108.193) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org On 07/01/2022 11:12, Ajish.Koshy@microchip.com wrote: >> Once the task is dispatched to HW at ****, it is completed async, i.e. >> it may be completed and freed at any point, even before the dispatch >> function returns. So it is illegal to touch the task at this point and the task >> state must be updated before final dispatch to the HW. If you enable KASAN >> you will prob see it yell like I saw. >> > I too have similar thought here. After dispatch to HW, no point to touch the > task state. But since the code is in IO path, may need further testing. > Hi, Have you made any progress on the hang which I see on my arm64 system? I think that you said that you can also see it on an arm64 system - would that be with a similar card to mine? I think mine is 8008/9 I have tested some older kernels and v4.11 seems much better. Thanks, John