From: Andi Shyti <andi.shyti@kernel.org>
To: Alexey Charkov <alchark@gmail.com>
Cc: Wentao Liang <vulab@iscas.ac.cn>,
krzk@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@prisktech.co.nz, wsa@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 04/20] i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()
Date: Sat, 10 Oct 2026 16:34:23 +0200 [thread overview]
Message-ID: <aspGdlG2J4h6KxFl@zenone.zhora.eu> (raw)
In-Reply-To: <CABjd4YzNzZ0nnO4Xgw1JsRHhj9Crc6diX1uJnWHpHvd6BcPk2g@mail.gmail.com>
Hi Wentao,
On Wed, Sep 16, 2026 at 11:17:49AM +0400, Alexey Charkov wrote:
> On Wed, Sep 16, 2026 at 11:07 AM Wentao Liang <vulab@iscas.ac.cn> wrote:
> >
> > In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any
> > subsequent operation fails or when the module is unloaded, the clock
> > reference count is never decremented via clk_put(), leading to a
> > resource leak.
> >
> > Switch to devm_clk_get() so that the clock is automatically managed
> > and released.
> >
> > Fixes: 560746eb79d3 ("i2c: vt8500: Add support for I2C bus on Wondermedia SoCs")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
this is 4/20 but where are the rest of the patches?
> > ---
> > drivers/i2c/busses/i2c-viai2c-wmt.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/i2c/busses/i2c-viai2c-wmt.c b/drivers/i2c/busses/i2c-viai2c-wmt.c
> > index 2cf3cc0165fb..74ca93b44347 100644
> > --- a/drivers/i2c/busses/i2c-viai2c-wmt.c
> > +++ b/drivers/i2c/busses/i2c-viai2c-wmt.c
> > @@ -117,7 +117,7 @@ static int wmt_i2c_probe(struct platform_device *pdev)
> > return dev_err_probe(&pdev->dev, err,
> > "failed to request irq %i\n", i2c->irq);
> >
> > - i2c->clk = of_clk_get(np, 0);
> > + i2c->clk = devm_clk_get(&pdev->dev, NULL);
>
> Maybe we could go for devm_clk_get_enabled and drop some more
> boilerplate which follows in wmt_i2c_reset_hardware, while at it?
>
> Backporting this to stable seems like a stretch to me, though (it's
> quite old code, so there would be quite a lot of backporting for a
> rarely hit resource leak).
Alexey asked a question. Wouldn't it be good to follow up?
Unfortunately, this is becoming quite common with LLM generated
patches, where questions are often left unanswered, perhaps
because the patches are not fully understood by committers.
I think the patch is correct, though, and Alexey's suggestions
can be addressed after this is merged.
With some disappointment, I'm pushing this patch to
i2c/i2c-fixes-2.
Andi
prev parent reply other threads:[~2026-10-10 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 7:06 Wentao Liang
2026-09-16 7:17 ` Alexey Charkov
2026-10-10 14:34 ` Andi Shyti [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=aspGdlG2J4h6KxFl@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=alchark@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
--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
all inboxes | Powered by JetHome®