[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173957268922.110887.5172881427439356224.b4-ty@kernel.org>
Date: Fri, 14 Feb 2025 16:38:20 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: konradybcio@...nel.org,
Mukesh Ojha <mukesh.ojha@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Saranya R <quic_sarar@...cinc.com>,
stable@...r.kernel.org,
Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH v3] soc: qcom: pdr: Fix the potential deadlock
On Wed, 12 Feb 2025 22:07:20 +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.
>
> [...]
Applied, thanks!
[1/1] soc: qcom: pdr: Fix the potential deadlock
commit: 2eeb03ad9f42dfece63051be2400af487ddb96d2
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists