Received: by 2002:a05:7412:2a8c:b0:e2:908c:2ebd with SMTP id u12csp955121rdh; Sun, 24 Sep 2023 20:50:08 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGTnNVoHOhRDo2wSgiWPt0/TaT9jogxNgMeD+FG69vnrI4eXjLuUU1WyFkNlajf1wu4OW3J X-Received: by 2002:a05:6a00:a04:b0:690:d718:8c6d with SMTP id p4-20020a056a000a0400b00690d7188c6dmr4517825pfh.15.1695613807706; Sun, 24 Sep 2023 20:50:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695613807; cv=none; d=google.com; s=arc-20160816; b=koucBUE6EauMfdr1dWKavAOnisaIsCG+FEuvYlNdO7EspZw76H2AzPpvpGzwc0iVse wzDt+75q7NAHZioTCAfUO5lvrKmntET6tqSGbkGusQ9TIrftfHvILWqiJw0fBvGcp9YX ksqwWE1qOkb7Gog1C0n8toulBnbyORX+GxE9epicMmdJWdy+k/twfMpbdKB4IyO8/9ac zBj2yCHkgcd6uTmmXk0dMyK1q3MFpj42ZuZiwGrmCRbxjt8jSP76teLInwpz6eVK3vrY E9EbZG/w/dgKsm2U3qYwNRKH2QMLlV6eqW+nlMad71XvS4SUIfrxI3T64iQJRAU/17hn mbFA== 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 :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=30VHeSyGYzHPzTB3jvCEkL+AUpeDSctcovuhd0vnFV0=; fh=aBMVh6AOhLx4o5pw1hD1V14giOQOFybSEhyUqSShgIc=; b=uq4QhAiY2L4BKMpPlipAVC1HVfSmeG0508qo45+XkYKdLM1f9ydHFVThbhcNv5j+SL 7lpy+BRp5BQxRzoOvGz4ogH5u/F0u+TuFeIunhNVopmeqvOd72BPDHNrKQGxBnPwD3fp lzJv+FArTboH93Woahxhkkw6aNX0wwO5NHFf+y1RzfQswOn2xTdGOrXRhaWhWhDXHgC5 DHXyJXgGzLxowxNIiytC2mra0vQnbHRNOO0HIm02LC3TYPUI+BCTZ2hctaJ07p3SV2nL bZhJZ1gCoTDjmgPBqbkjuAnn5T+7s4YRNhUdyWpJyY7W1hXuotnvVo98m+ic8S1IKfG/ pHOA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="f/RjTU52"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Return-Path: Received: from agentk.vger.email (agentk.vger.email. [23.128.96.32]) by mx.google.com with ESMTPS id ef7-20020a056a002c8700b00689f1186cfdsi9231686pfb.29.2023.09.24.20.50.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 24 Sep 2023 20:50:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="f/RjTU52"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id D01878198C67; Sun, 24 Sep 2023 20:10:46 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230218AbjIYDKn (ORCPT + 99 others); Sun, 24 Sep 2023 23:10:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51458 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230163AbjIYDKm (ORCPT ); Sun, 24 Sep 2023 23:10:42 -0400 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 90BFAA7; Sun, 24 Sep 2023 20:10:32 -0700 (PDT) Received: from pps.filterd (m0279868.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 38P2w9rj014284; Mon, 25 Sep 2023 03:10:21 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=30VHeSyGYzHPzTB3jvCEkL+AUpeDSctcovuhd0vnFV0=; b=f/RjTU52f7b3pYQYD2fEZT2Qvr14BxjU9A3OPNfdYgQ0rSY1eF12HDtIlYXz+x2eM7BM slZtfedheae0MGva7FbcezRLAeAL/Mh+F/ASnUY7Pwc9W4bwqGhKK5mKtlv8/YpQL2Hi 6TwedjDF5MzqieedOZU5v0TUrN4qKxuw8+cB+nhkTVVQJrEz9QuTKHJQtg9fpBh6wLCK osy/EMZpSlP1LWLl5Vugf8euA/Er2xKkHvH4QfblZuq5e/dGAYSy4YxjOq1TGcnQ7N8C /uMQyPthOrxx9Bw2JZwyYTWlPeJJRL25t9zF67PHRiIZlZ6zyHMcIz3PASepg5OC1W7o jA== Received: from nasanppmta03.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3t9qbptjcb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Sep 2023 03:10:20 +0000 Received: from nasanex01a.na.qualcomm.com (nasanex01a.na.qualcomm.com [10.52.223.231]) by NASANPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 38P3AJwQ031384 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Sep 2023 03:10:19 GMT Received: from [10.253.15.18] (10.80.80.8) by nasanex01a.na.qualcomm.com (10.52.223.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.36; Sun, 24 Sep 2023 20:10:16 -0700 Message-ID: Date: Mon, 25 Sep 2023 11:10:06 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: [PATCH v2 1/2] bus: mhi: host: Add spinlock to protect WP access when queueing TREs To: Jeffrey Hugo , CC: , , , , References: <1694594861-12691-1-git-send-email-quic_qianyu@quicinc.com> <1694594861-12691-2-git-send-email-quic_qianyu@quicinc.com> Content-Language: en-US From: Qiang Yu In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nasanex01a.na.qualcomm.com (10.52.223.231) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: XJRBA2dU3AwcwaB447MKd2S34rCXhU9g X-Proofpoint-ORIG-GUID: XJRBA2dU3AwcwaB447MKd2S34rCXhU9g X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-24_21,2023-09-21_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 priorityscore=1501 adultscore=0 mlxlogscore=999 spamscore=0 malwarescore=0 impostorscore=0 lowpriorityscore=0 phishscore=0 suspectscore=0 clxscore=1015 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2309180000 definitions=main-2309250018 X-Spam-Status: No, score=-2.3 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 agentk.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 (agentk.vger.email [0.0.0.0]); Sun, 24 Sep 2023 20:10:46 -0700 (PDT) On 9/22/2023 10:44 PM, Jeffrey Hugo wrote: > On 9/13/2023 2:47 AM, Qiang Yu wrote: >> From: Bhaumik Bhatt >> >> Protect WP accesses such that multiple threads queueing buffers for >> incoming data do not race and access the same WP twice. Ensure read and >> write locks for the channel are not taken in succession by dropping the >> read lock from parse_xfer_event() such that a callback given to client >> can potentially queue buffers and acquire the write lock in that >> process. >> Any queueing of buffers should be done without channel read lock >> acquired >> as it can result in multiple locks and a soft lockup. >> >> Signed-off-by: Bhaumik Bhatt >> Signed-off-by: Qiang Yu >> --- >>   drivers/bus/mhi/host/main.c | 11 ++++++++++- >>   1 file changed, 10 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/bus/mhi/host/main.c b/drivers/bus/mhi/host/main.c >> index dcf627b..13c4b89 100644 >> --- a/drivers/bus/mhi/host/main.c >> +++ b/drivers/bus/mhi/host/main.c >> @@ -642,6 +642,7 @@ static int parse_xfer_event(struct mhi_controller >> *mhi_cntrl, >>               mhi_del_ring_element(mhi_cntrl, tre_ring); >>               local_rp = tre_ring->rp; >>   +            read_unlock_bh(&mhi_chan->lock); > > This doesn't work due to the write_lock_irqsave(&mhi_chan->lock, > flags); on line 591. Write_lock_irqsave(&mhi_chan->lock, flags) is used in case of ev_code >= MHI_EV_CC_OOB. We only read_lock/read_unlock the mhi_chan while ev_code < MHI_EV_CC_OOB. > > I really don't like that we are unlocking the mhi_chan while still > using it.  It opens up a window where the mhi_chan state can be > updated between here and the client using the callback to queue a buf. > > Perhaps we need a new lock that just protects the wp, and needs to be > only grabbed while mhi_chan->lock is held? Since we have employed mhi_chan lock to protect the channel and what we are concerned here is that client may queue buf to a disabled or stopped channel, can we check channel state after getting mhi_chan->lock like line 595. We can add the check after getting write lock in mhi_gen_tre() and after getting read lock again here. > >>               /* notify client */ >>               mhi_chan->xfer_cb(mhi_chan->mhi_dev, &result); >>   @@ -667,6 +668,7 @@ static int parse_xfer_event(struct >> mhi_controller *mhi_cntrl, >>                       kfree(buf_info->cb_buf); >>                   } >>               } >> +            read_lock_bh(&mhi_chan->lock); >>           } >>           break; >>       } /* CC_EOT */ >> @@ -1204,6 +1206,9 @@ int mhi_gen_tre(struct mhi_controller >> *mhi_cntrl, struct mhi_chan *mhi_chan, >>       int eot, eob, chain, bei; >>       int ret; >>   +    /* Protect accesses for reading and incrementing WP */ >> +    write_lock_bh(&mhi_chan->lock); >> + >>       buf_ring = &mhi_chan->buf_ring; >>       tre_ring = &mhi_chan->tre_ring; >>   @@ -1221,8 +1226,10 @@ int mhi_gen_tre(struct mhi_controller >> *mhi_cntrl, struct mhi_chan *mhi_chan, >>         if (!info->pre_mapped) { >>           ret = mhi_cntrl->map_single(mhi_cntrl, buf_info); >> -        if (ret) >> +        if (ret) { >> +            write_unlock_bh(&mhi_chan->lock); >>               return ret; >> +        } >>       } >>         eob = !!(flags & MHI_EOB); >> @@ -1239,6 +1246,8 @@ int mhi_gen_tre(struct mhi_controller >> *mhi_cntrl, struct mhi_chan *mhi_chan, >>       mhi_add_ring_element(mhi_cntrl, tre_ring); >>       mhi_add_ring_element(mhi_cntrl, buf_ring); >>   +    write_unlock_bh(&mhi_chan->lock); >> + >>       return 0; >>   } >