From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: konradybcio@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Saranya R <quic_sarar@quicinc.com>,
Johan Hovold <johan@kernel.org>,
Frank Oltmanns <frank@oltmanns.dev>
Subject: Re: [PATCH v2] soc: qcom: pdr: Fix the potential deadlock
Date: Mon, 10 Feb 2025 14:50:18 +0530 [thread overview]
Message-ID: <Z6nE0kxF2ipItB2r@hu-mojha-hyd.qualcomm.com> (raw)
In-Reply-To: <nqsuml3jcblwkp6mcriiekfiz5wlxjypooiygvgd5fjtmfnvdc@zfoaolcjecpl>
On Thu, Feb 06, 2025 at 04:13:25PM -0600, Bjorn Andersson wrote:
> On Wed, Jan 29, 2025 at 09:25:44PM +0530, Mukesh Ojha wrote:
> > When some client process A call pdr_add_lookup() to add the look up for
> > the service and does schedule locator work, later a process B got a new
> > server packet indicating locator is up and call pdr_locator_new_server()
> > which eventually sets pdr->locator_init_complete to true which process A
> > sees and takes list lock and queries domain list but it will timeout due
> > to deadlock as the response will queued to the same qmi->wq and it is
> > ordered workqueue and process B is not able to complete new server
> > request work due to deadlock on list lock.
> >
> > Process A Process B
> >
> > process_scheduled_works()
> > pdr_add_lookup() qmi_data_ready_work()
> > process_scheduled_works() pdr_locator_new_server()
> > pdr->locator_init_complete=true;
> > pdr_locator_work()
> > mutex_lock(&pdr->list_lock);
> >
> > pdr_locate_service() mutex_lock(&pdr->list_lock);
> >
> > pdr_get_domain_list()
> > pr_err("PDR: %s get domain list
> > txn wait failed: %d\n",
> > req->service_name,
> > ret);
> >
> > Fix it by removing the unnecessary list iteration as the list iteration
> > is already being done inside locator work, so avoid it here and just
> > call schedule_work() here.
> >
>
> I came to the same patch while looking into the issue related to
> in-kernel pd-mapper reported here:
> https://lore.kernel.org/lkml/Zqet8iInnDhnxkT9@hovoldconsulting.com/
>
> So:
> Reviewed-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> Tested-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Thanks.,
>
> > Fixes: fbe639b44a82 ("soc: qcom: Introduce Protection Domain Restart helpers")
> > CC: stable@vger.kernel.org
> > Signed-off-by: Saranya R <quic_sarar@quicinc.com>
>
> Can we please use full names?
I have informed her about this and she wants the same name to be mentioned here as well.
>
> > Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
>
> Unfortunately I can't merge this; Saranya's S-o-b comes first which
> implies that she authored the patch, but you're listed as author.
I will correct it.
-Mukesh
>
> Regards,
> Bjorn
>
> > ---
> > Changes in v2:
> > - Added Fixes tag,
> >
> > drivers/soc/qcom/pdr_interface.c | 8 +-------
> > 1 file changed, 1 insertion(+), 7 deletions(-)
> >
> > diff --git a/drivers/soc/qcom/pdr_interface.c b/drivers/soc/qcom/pdr_interface.c
> > index 328b6153b2be..71be378d2e43 100644
> > --- a/drivers/soc/qcom/pdr_interface.c
> > +++ b/drivers/soc/qcom/pdr_interface.c
> > @@ -75,7 +75,6 @@ static int pdr_locator_new_server(struct qmi_handle *qmi,
> > {
> > struct pdr_handle *pdr = container_of(qmi, struct pdr_handle,
> > locator_hdl);
> > - struct pdr_service *pds;
> >
> > mutex_lock(&pdr->lock);
> > /* Create a local client port for QMI communication */
> > @@ -87,12 +86,7 @@ static int pdr_locator_new_server(struct qmi_handle *qmi,
> > mutex_unlock(&pdr->lock);
> >
> > /* Service pending lookup requests */
> > - mutex_lock(&pdr->list_lock);
> > - list_for_each_entry(pds, &pdr->lookups, node) {
> > - if (pds->need_locator_lookup)
> > - schedule_work(&pdr->locator_work);
> > - }
> > - mutex_unlock(&pdr->list_lock);
> > + schedule_work(&pdr->locator_work);
> >
> > return 0;
> > }
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-02-10 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 15:55 [PATCH v2] soc: qcom: pdr: Fix the potential deadlock Mukesh Ojha
2025-02-06 22:13 ` Bjorn Andersson
2025-02-10 9:20 ` Mukesh Ojha [this message]
2025-02-10 9:43 ` Johan Hovold
2025-02-11 17:07 ` Mukesh Ojha
2025-02-12 9:37 ` Johan Hovold
2025-02-12 10:59 ` Johan Hovold
2025-02-12 16:13 ` Mukesh Ojha
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=Z6nE0kxF2ipItB2r@hu-mojha-hyd.qualcomm.com \
--to=mukesh.ojha@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=frank@oltmanns.dev \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_sarar@quicinc.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).