From: Manivannan Sadhasivam <mani@kernel.org>
To: Qiang Yu <quic_qianyu@quicinc.com>
Cc: quic_jhugo@quicinc.com, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_cang@quicinc.com, quic_mrana@quicinc.com
Subject: Re: [PATCH v5 0/2] bus: mhi: host: Add lock to avoid race when ringing channel DB
Date: Sat, 16 Dec 2023 10:51:32 +0530 [thread overview]
Message-ID: <20231216052132.GC3405@thinkpad> (raw)
In-Reply-To: <1702276972-41296-1-git-send-email-quic_qianyu@quicinc.com>
On Mon, Dec 11, 2023 at 02:42:50PM +0800, Qiang Yu wrote:
>
> 1. We need a write lock in mhi_gen_tre otherwise there is race of the WP
> used for ringing channel DB between mhi_queue and M0 transition.
> 2. We can not invoke local_bh_enable() when irqs are disabled, so move
> read_lock_irqsave() under the mhi_gen_tre() since we add write_lock_bh() in
> mhi_gen_tre().
> 3. Unlock xfer_cb to prevent potential lockup
>
Applied to mhi-next!
- Mani
> v1 -> v2:
> Added write_unlock_bh(&mhi_chan->lock) in mhi_gen_tre() before return
> because of error process.
>
> v2 -> v3:
> 1. split protecting WP and unlocking xfer_cb into two patches
> 2. Add a new patch to stop processing buffer and eventof a disabled or
> stopped channel.
>
> v3 -> v4:
> 1. Modify commit message
> 2. Add unlock operation before return error
>
> v4 -> v5:
> 1. Squash "protecting WP" and "Take irqsave lock" into one patch
> 2. Drop patch 3/4 of patch v4
>
> Bhaumik Bhatt (1):
> bus: mhi: host: Add spinlock to protect WP access when queueing TREs
>
> Qiang Yu (1):
> bus: mhi: host: Drop chan lock before queuing buffers
>
> drivers/bus/mhi/host/main.c | 26 +++++++++++++++++---------
> 1 file changed, 17 insertions(+), 9 deletions(-)
>
> --
> 2.7.4
>
>
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2023-12-16 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 6:42 [PATCH v5 0/2] bus: mhi: host: Add lock to avoid race when ringing channel DB Qiang Yu
2023-12-11 6:42 ` [PATCH v5 1/2] bus: mhi: host: Add spinlock to protect WP access when queueing TREs Qiang Yu
2023-12-15 18:23 ` Jeffrey Hugo
2023-12-16 5:15 ` Manivannan Sadhasivam
2023-12-11 6:42 ` [PATCH v5 2/2] bus: mhi: host: Drop chan lock before queuing buffers Qiang Yu
2023-12-15 18:23 ` Jeffrey Hugo
2023-12-16 5:19 ` Manivannan Sadhasivam
2023-12-16 5:21 ` Manivannan Sadhasivam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231216052132.GC3405@thinkpad \
--to=mani@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_cang@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_qianyu@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox