From: Stepan Ionichev <sozdayvek@gmail.com>
To: wbg@kernel.org
Cc: patrick.havelange@essensium.com, peng.fan@nxp.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
andy@kernel.org, sozdayvek@gmail.com
Subject: [PATCH v2] counter: ftm-quaddec: use devm_mutex_init()
Date: Mon, 25 May 2026 20:12:40 +0500 [thread overview]
Message-ID: <20260525151240.7258-1-sozdayvek@gmail.com> (raw)
ftm_quaddec_probe() calls mutex_init() but neither the cleanup
action nor a remove callback issues a matching mutex_destroy(),
which leaks the lock debug state when CONFIG_DEBUG_MUTEXES is
enabled.
Switch to devm_mutex_init() so the mutex is torn down in the same
devm scope it was set up in.
Fixes: a3b9a99980d9 ("counter: add FlexTimer Module Quadrature decoder counter driver")
Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
---
v2:
- Add Fixes tag and note that the leak only shows up under
CONFIG_DEBUG_MUTEXES (William, applied from the interrupt-cnt thread)
v1: https://lore.kernel.org/all/20260523184351.7567-1-sozdayvek@gmail.com/
drivers/counter/ftm-quaddec.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/counter/ftm-quaddec.c b/drivers/counter/ftm-quaddec.c
index c47741292..8455f16d6 100644
--- a/drivers/counter/ftm-quaddec.c
+++ b/drivers/counter/ftm-quaddec.c
@@ -292,7 +292,9 @@ static int ftm_quaddec_probe(struct platform_device *pdev)
counter->signals = ftm_quaddec_signals;
counter->num_signals = ARRAY_SIZE(ftm_quaddec_signals);
- mutex_init(&ftm->ftm_quaddec_mutex);
+ ret = devm_mutex_init(&pdev->dev, &ftm->ftm_quaddec_mutex);
+ if (ret)
+ return ret;
ftm_quaddec_init(ftm);
--
2.43.0
next reply other threads:[~2026-05-25 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 15:12 Stepan Ionichev [this message]
2026-05-26 10:24 ` Joshua Crofts
2026-05-27 16:57 ` Jonathan Cameron
2026-05-27 21:52 ` William Breathitt Gray
2026-05-28 13:07 ` Jonathan Cameron
2026-05-29 2:08 ` William Breathitt Gray
2026-05-27 7:02 ` William Breathitt Gray
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=20260525151240.7258-1-sozdayvek@gmail.com \
--to=sozdayvek@gmail.com \
--cc=andy@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.havelange@essensium.com \
--cc=peng.fan@nxp.com \
--cc=wbg@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®