Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3053807imu; Sun, 6 Jan 2019 17:37:45 -0800 (PST) X-Google-Smtp-Source: ALg8bN4/STzLqJr1DgAIF99YG5+TFr1SrqpenkQC6QtaWmhz4Fa4C0jvAQlBZz/qfbBLSGEETmxT X-Received: by 2002:a17:902:a03:: with SMTP id 3mr59795471plo.112.1546825065289; Sun, 06 Jan 2019 17:37:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546825065; cv=none; d=google.com; s=arc-20160816; b=0MS7sc+Os4ZrtJTOi6JjIFj4LjJnAYAKka2sLefkkleafYbbu/BX5+n8Bn72zEeI8w JLw39KagqFobEUCbu6iQjFDKbxk29JqUsn5jMNoeU3kHEwCAvvg7If8FffT0auDyUQPd W9pE3JMVu7nK3ixDAyQmWVPDRdYtu3iVOwDeZbo4zaMMy7WQFe0guUdtNhpKz/Ces0d3 1etJyHJNY4FmbeUabR+sTcmFGntJiEEvW8H4TcnsgmTZeUhu858gyhN8nutbpM4+PqtI 0wDt9qprfzQzcKyUZvWgZriVbm6wF+nhwmgyxcL/hJUxBKOliM//JAOQ10mjEMrGT6xM oXpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=zL3vKTrogZJygne3ZEC9ktcn4ikr40nSzXTvHRlM4y0=; b=tauVtiet1L6HkfGY3WqLGC/FG7Bd2O1EYH4NtQU+bHg+ygkkodzp48Po63g+5m+qda 02GVqEUXvgieRh7U9Zs6l0EnxzoxADRjIMZLlMnKyZsx9ekDlcLqZTp7reBXmm7QVKnL K1rz5oZKJEt4zJ8+OweoXxYIJ2KV9h3CT5Ittda5tgwfN4v37N/Qg+9Ww5d5BW0EQ6yj D+PGn/0fOyR9PUqQw0Yi+zpWbuqAa3XozRO0G6d+r3rYfFnom/JKZVpquYxaY2xYgDhJ WXvr864w4wiieKbZnId/JcE2XK4ja2K9C34RyGrSRhKdC51SAlhMkvOuWC3veMscXQQz Fu2g== 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 37si3593987pgw.590.2019.01.06.17.37.30; Sun, 06 Jan 2019 17:37:45 -0800 (PST) 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 S1726330AbfAGBek (ORCPT + 99 others); Sun, 6 Jan 2019 20:34:40 -0500 Received: from [38.106.11.25] ([38.106.11.25]:47454 "EHLO barracuda02.hxt-semitech.com" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726287AbfAGBek (ORCPT ); Sun, 6 Jan 2019 20:34:40 -0500 X-ASG-Debug-ID: 1546824874-107606139f12fb70001-xx1T2L Received: from HXTBJIDCEMVIW02.hxtcorp.net ([10.128.0.15]) by barracuda02.hxt-semitech.com with ESMTP id KyFKKd0JQUYkqUXH (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Mon, 07 Jan 2019 09:34:34 +0800 (CST) X-Barracuda-Envelope-From: shunyong.yang@hxt-semitech.com Received: from y.localdomain (10.5.21.109) by HXTBJIDCEMVIW02.hxtcorp.net (10.128.0.15) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 7 Jan 2019 09:34:29 +0800 From: Shunyong Yang To: CC: , , , , , , Shunyong Yang , Joey Zheng Subject: [PATCH v2 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Date: Mon, 7 Jan 2019 09:34:02 +0800 X-ASG-Orig-Subj: [PATCH v2 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Message-ID: <9e49721af4f2aee61045e755cc3359d192c9a75a.1546823811.git.shunyong.yang@hxt-semitech.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <8109d1ab70fe6dbacdbe89fda38d8dcb450c884c.1546823811.git.shunyong.yang@hxt-semitech.com> References: <8109d1ab70fe6dbacdbe89fda38d8dcb450c884c.1546823811.git.shunyong.yang@hxt-semitech.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.5.21.109] X-ClientProxiedBy: HXTBJIDCEMVIW02.hxtcorp.net (10.128.0.15) To HXTBJIDCEMVIW02.hxtcorp.net (10.128.0.15) X-Barracuda-Connect: UNKNOWN[10.128.0.15] X-Barracuda-Start-Time: 1546824874 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA384 X-Barracuda-URL: https://192.168.50.102:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 3011 X-Virus-Scanned: by bsmtpd at hxt-semitech.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.4656 1.0000 0.0000 X-Barracuda-Spam-Score: 0.50 X-Barracuda-Spam-Status: No, SCORE=0.50 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_RULE_7582B X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.65247 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.50 BSF_RULE_7582B Custom Rule 7582B Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When dma_cookie_complete() is called in hidma_process_completed(), dma_cookie_status() will return DMA_COMPLETE in hidma_tx_status(). Then, hidma_txn_is_success() will be called to use channel cookie mchan->last_success to do additional DMA status check. Current code assigns mchan->last_success after dma_cookie_complete(). This causes a race condition of dma_cookie_status() returns DMA_COMPLETE before mchan->last_success is assigned correctly. The race will cause hidma_tx_status() return DMA_ERROR but the transaction is actually a success. Moreover, in async_tx case, it will cause a timeout panic in async_tx_quiesce(). Kernel panic - not syncing: async_tx_quiesce: DMA error waiting for transaction ... Call trace: [] dump_backtrace+0x0/0x1f4 [] show_stack+0x24/0x2c [] dump_stack+0x84/0xa8 [] panic+0x12c/0x29c [] async_tx_quiesce+0xa4/0xc8 [async_tx] [] async_trigger_callback+0x70/0x1c0 [async_tx] [] raid_run_ops+0x86c/0x1540 [raid456] [] handle_stripe+0x5e8/0x1c7c [raid456] [] handle_active_stripes.isra.45+0x2d4/0x550 [raid456] [] raid5d+0x38c/0x5d0 [raid456] [] md_thread+0x108/0x168 [] kthread+0x10c/0x138 [] ret_from_fork+0x10/0x18 Cc: Joey Zheng Reviewed-by: Sinan Kaya Signed-off-by: Shunyong Yang --- v2: fix missing brace according to Vinod's feedback. add Reviewed-by: Sinan Kaya . --- drivers/dma/qcom/hidma.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/drivers/dma/qcom/hidma.c b/drivers/dma/qcom/hidma.c index 9d639ed1955a..411f91fde734 100644 --- a/drivers/dma/qcom/hidma.c +++ b/drivers/dma/qcom/hidma.c @@ -138,24 +138,25 @@ static void hidma_process_completed(struct hidma_chan *mchan) desc = &mdesc->desc; last_cookie = desc->cookie; + llstat = hidma_ll_status(mdma->lldev, mdesc->tre_ch); + spin_lock_irqsave(&mchan->lock, irqflags); + if (llstat == DMA_COMPLETE) { + mchan->last_success = last_cookie; + result.result = DMA_TRANS_NOERROR; + } else { + result.result = DMA_TRANS_ABORTED; + } + dma_cookie_complete(desc); spin_unlock_irqrestore(&mchan->lock, irqflags); - llstat = hidma_ll_status(mdma->lldev, mdesc->tre_ch); dmaengine_desc_get_callback(desc, &cb); dma_run_dependencies(desc); spin_lock_irqsave(&mchan->lock, irqflags); list_move(&mdesc->node, &mchan->free); - - if (llstat == DMA_COMPLETE) { - mchan->last_success = last_cookie; - result.result = DMA_TRANS_NOERROR; - } else - result.result = DMA_TRANS_ABORTED; - spin_unlock_irqrestore(&mchan->lock, irqflags); dmaengine_desc_callback_invoke(&cb, &result); -- 1.8.3.1