From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 4/9] i2c: qcom-cci: don't put a device tree node before i2c_add_adapter()
Date: Fri, 4 Feb 2022 10:11:32 -0800 [thread overview]
Message-ID: <Yf1sVGfHwrSMX4WA@ripper> (raw)
In-Reply-To: <20220203164703.1712006-1-vladimir.zapolskiy@linaro.org>
On Thu 03 Feb 08:47 PST 2022, Vladimir Zapolskiy wrote:
> There is a minor chance for a race, if a pointer to an i2c-bus subnode
> is stored and then reused after releasing its reference, and it would
> be sufficient to get one more reference under a loop over children
> subnodes.
>
> Fixes: e517526195de ("i2c: Add Qualcomm CCI I2C driver")
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> ---
> drivers/i2c/busses/i2c-qcom-cci.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-qcom-cci.c b/drivers/i2c/busses/i2c-qcom-cci.c
> index fd4260d18577..cf54f1cb4c57 100644
> --- a/drivers/i2c/busses/i2c-qcom-cci.c
> +++ b/drivers/i2c/busses/i2c-qcom-cci.c
> @@ -558,7 +558,7 @@ static int cci_probe(struct platform_device *pdev)
> cci->master[idx].adap.quirks = &cci->data->quirks;
> cci->master[idx].adap.algo = &cci_algo;
> cci->master[idx].adap.dev.parent = dev;
> - cci->master[idx].adap.dev.of_node = child;
> + cci->master[idx].adap.dev.of_node = of_node_get(child);
> cci->master[idx].master = idx;
> cci->master[idx].cci = cci;
>
> @@ -643,8 +643,10 @@ static int cci_probe(struct platform_device *pdev)
> continue;
>
> ret = i2c_add_adapter(&cci->master[i].adap);
> - if (ret < 0)
> + if (ret < 0) {
> + of_node_put(cci->master[i].adap.dev.of_node);
> goto error_i2c;
> + }
> }
>
> pm_runtime_set_autosuspend_delay(dev, MSEC_PER_SEC);
> @@ -656,8 +658,10 @@ static int cci_probe(struct platform_device *pdev)
>
> error_i2c:
> for (--i ; i >= 0; i--) {
> - if (cci->master[i].cci)
> + if (cci->master[i].cci) {
> i2c_del_adapter(&cci->master[i].adap);
> + of_node_put(cci->master[i].adap.dev.of_node);
> + }
> }
> error:
> disable_irq(cci->irq);
> @@ -673,8 +677,10 @@ static int cci_remove(struct platform_device *pdev)
> int i;
>
> for (i = 0; i < cci->data->num_masters; i++) {
> - if (cci->master[i].cci)
> + if (cci->master[i].cci) {
> i2c_del_adapter(&cci->master[i].adap);
> + of_node_put(cci->master[i].adap.dev.of_node);
> + }
> cci_halt(cci, i);
> }
>
> --
> 2.33.0
>
next prev parent reply other threads:[~2022-02-04 18:11 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 16:46 [PATCH 0/9] i2c: qcom-cci: fixes and updates Vladimir Zapolskiy
2022-02-03 16:46 ` [PATCH 1/9] dt-bindings: i2c: qcom-cci: add QCOM SM8450 compatible Vladimir Zapolskiy
2022-02-04 11:04 ` Robert Foss
2022-02-11 14:12 ` Rob Herring
2022-02-18 9:02 ` Wolfram Sang
2022-02-03 16:46 ` [PATCH 2/9] dt-bindings: i2c: qcom-cci: add description of a vbus-supply property Vladimir Zapolskiy
2022-02-04 11:06 ` Robert Foss
2022-02-04 18:05 ` Bjorn Andersson
2022-02-04 18:42 ` Mark Brown
2022-02-04 19:02 ` Bjorn Andersson
2022-02-04 19:32 ` Mark Brown
2022-02-07 14:08 ` Vladimir Zapolskiy
2022-02-07 14:39 ` Mark Brown
2022-02-07 18:31 ` Vladimir Zapolskiy
2022-02-08 12:55 ` Mark Brown
2022-02-10 15:33 ` Dmitry Baryshkov
2022-02-10 15:44 ` Mark Brown
2022-02-10 17:32 ` Dmitry Baryshkov
2022-02-10 17:36 ` Mark Brown
2022-02-10 18:21 ` Dmitry Baryshkov
2022-02-10 18:26 ` Mark Brown
2022-02-10 19:02 ` Dmitry Baryshkov
2022-02-03 16:47 ` [PATCH 3/9] i2c: qcom-cci: don't delete an unregistered adapter Vladimir Zapolskiy
2022-02-04 10:05 ` Robert Foss
2022-02-04 18:08 ` Bjorn Andersson
2022-02-11 17:45 ` Wolfram Sang
2022-02-11 17:43 ` Wolfram Sang
2022-02-03 16:47 ` [PATCH 4/9] i2c: qcom-cci: don't put a device tree node before i2c_add_adapter() Vladimir Zapolskiy
2022-02-04 10:17 ` Robert Foss
2022-02-04 18:11 ` Bjorn Andersson [this message]
2022-02-11 17:44 ` Wolfram Sang
2022-02-03 16:47 ` [PATCH 5/9] i2c: qcom-cci: initialize CCI controller after registration of adapters Vladimir Zapolskiy
2022-02-03 17:29 ` Loic Poulain
2022-02-03 18:45 ` Vladimir Zapolskiy
2022-02-04 11:18 ` Loic Poulain
2022-02-04 18:31 ` Bjorn Andersson
2022-02-03 16:47 ` [PATCH 6/9] i2c: qcom-cci: simplify probe by removing one loop over busses Vladimir Zapolskiy
2022-02-04 10:20 ` Robert Foss
2022-02-03 16:47 ` [PATCH 7/9] i2c: qcom-cci: simplify access to bus data structure Vladimir Zapolskiy
2022-02-04 10:21 ` Robert Foss
2022-02-03 16:47 ` [PATCH 8/9] i2c: qcom-cci: add support of optional vbus-supply regulators Vladimir Zapolskiy
2022-02-04 11:03 ` Robert Foss
2022-02-04 11:41 ` Loic Poulain
2022-02-04 18:28 ` Bjorn Andersson
2022-02-10 15:37 ` Dmitry Baryshkov
2022-02-04 18:21 ` Bjorn Andersson
2022-02-03 16:47 ` [PATCH 9/9] i2c: qcom-cci: add sm8450 compatible Vladimir Zapolskiy
2022-02-04 11:03 ` Robert Foss
2022-02-18 9:02 ` Wolfram Sang
2022-02-11 17:49 ` [PATCH 0/9] i2c: qcom-cci: fixes and updates Wolfram Sang
2022-02-11 19:46 ` Vladimir Zapolskiy
2022-02-11 20:43 ` Wolfram Sang
2022-02-17 19:57 ` Wolfram Sang
2022-02-17 21:47 ` Vladimir Zapolskiy
2022-02-18 9:05 ` Wolfram Sang
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=Yf1sVGfHwrSMX4WA@ripper \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=robert.foss@linaro.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wsa@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).