From: Yuho Choi <dbgh9129@gmail.com>
To: heikki.krogerus@linux.intel.com
Cc: gregkh@linuxfoundation.org, sebastian.reichel@collabora.com,
tglx@kernel.org, alchark@flipper.net,
u.kleine-koenig@baylibre.com, ustc.gu@gmail.com,
bigeasy@linutronix.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Yuho Choi <dbgh9129@gmail.com>
Subject: [PATCH v1] usb: typec: fusb302: Free log buffers on exit
Date: Fri, 7 Aug 2026 16:34:03 -0400 [thread overview]
Message-ID: <20260807203403.1011343-1-dbgh9129@gmail.com> (raw)
fusb302_log() lazily allocates entries in chip->logbuffer[], but
fusb302_debugfs_exit() only removes the debugfs directory. The buffers are
not part of the devm-managed chip allocation, so they leak when the driver
is removed or probe fails after logging.
Free all log buffer entries during debugfs teardown.
Fixes: c034a43e72dd ("staging: typec: Fairchild FUSB302 Type-c chip driver")
Signed-off-by: Yuho Choi <dbgh9129@gmail.com>
---
drivers/usb/typec/tcpm/fusb302.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/typec/tcpm/fusb302.c b/drivers/usb/typec/tcpm/fusb302.c
index 3319f6a2b0c9..67ccbbd64caf 100644
--- a/drivers/usb/typec/tcpm/fusb302.c
+++ b/drivers/usb/typec/tcpm/fusb302.c
@@ -223,7 +223,16 @@ static void fusb302_debugfs_init(struct fusb302_chip *chip)
static void fusb302_debugfs_exit(struct fusb302_chip *chip)
{
+ int i;
+
debugfs_remove(chip->dentry);
+
+ mutex_lock(&chip->logbuffer_lock);
+ for (i = 0; i < LOG_BUFFER_ENTRIES; i++) {
+ kfree(chip->logbuffer[i]);
+ chip->logbuffer[i] = NULL;
+ }
+ mutex_unlock(&chip->logbuffer_lock);
}
#else
@@ -1784,8 +1793,8 @@ static int fusb302_probe(struct i2c_client *client)
fwnode_put:
fwnode_handle_put(chip->tcpc_dev.fwnode);
destroy_workqueue:
- fusb302_debugfs_exit(chip);
destroy_workqueue(chip->wq);
+ fusb302_debugfs_exit(chip);
return ret;
}
--
2.43.0
next reply other threads:[~2026-08-07 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 20:34 Yuho Choi [this message]
2026-08-08 7:10 ` [PATCH v1] usb: typec: fusb302: Free log buffers on exit Greg KH
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=20260807203403.1011343-1-dbgh9129@gmail.com \
--to=dbgh9129@gmail.com \
--cc=alchark@flipper.net \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tglx@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=ustc.gu@gmail.com \
/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