[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c9948be1-4700-4aa5-9a63-10dc215fcff7@linaro.org>
Date: Sun, 7 Apr 2024 20:32:00 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-msm@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, Caleb Connolly <caleb.connolly@...aro.org>,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH] usb: typec: qcom-pmic-typec: split HPD bridge alloc and
registration
On 07/04/2024 16:08, Dmitry Baryshkov wrote:
> Basically, if for some reason (e.g. because the TCPM returns an error
> to one of the start functions) the drm_bridge is destroyed, the DRM
> driver isn't notified about the event. It still keeps the pointer to
> the bridge pointer and can access freed memory afterwards.
Hmm, my concern/question is about the TCPM code triggered by an IRQ
firing here, racing with the bridge code.
If you're happy you've reasoned about that and it won't happen, then
apply the ACK with the commit log fixed alone.
---
bod
Powered by blists - more mailing lists