From: Navaneeth K <knavaneeth786@gmail.com>
To: parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] most: core: fix resource leak in most_register_interface error paths
Date: Wed, 26 Nov 2025 04:40:27 +0530 [thread overview]
Message-ID: <de935747-acb4-4f08-a84e-e017b7d0f90c@gmail.com> (raw)
In-Reply-To: <20251125225606.70719-2-knavaneeth786@gmail.com>
Apologies, I missed adding the credit for the original finding.
If a v3 is needed for other reasons, I will include it. Otherwise, if
this is merged, please add:
Reported-by: Abdun Nihaal <abdun.nihaal@gmail.com>
On 26-11-2025 04:26, Navaneeth K wrote:
> The function most_register_interface() did not correctly release resources
> if it failed early (before device_register). In these cases, it returned
> an error code immediately, leaking the memory allocated for the interface.
>
> Fix this by initializing the device early via device_initialize() and
> calling put_device() on all error paths. This ensures the release
> callback is triggered to free memory.
>
> Switch to using device_add() instead of device_register() to handle
> the split initialization.
>
> Signed-off-by: Navaneeth K <knavaneeth786@gmail.com>
> ---
> drivers/most/core.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/most/core.c b/drivers/most/core.c
> index da319d108ea1d..8635fd08035e9 100644
> --- a/drivers/most/core.c
> +++ b/drivers/most/core.c
> @@ -1283,18 +1283,23 @@ int most_register_interface(struct most_interface *iface)
> struct most_channel *c;
>
> if (!iface || !iface->enqueue || !iface->configure ||
> - !iface->poison_channel || (iface->num_channels > MAX_CHANNELS))
> + !iface->poison_channel || (iface->num_channels > MAX_CHANNELS) ||
> + !iface->dev)
> return -EINVAL;
>
> + device_initialize(iface->dev);
> +
> id = ida_alloc(&mdev_id, GFP_KERNEL);
> if (id < 0) {
> dev_err(iface->dev, "Failed to allocate device ID\n");
> + put_device(iface->dev);
> return id;
> }
>
> iface->p = kzalloc(sizeof(*iface->p), GFP_KERNEL);
> if (!iface->p) {
> ida_free(&mdev_id, id);
> + put_device(iface->dev);
> return -ENOMEM;
> }
>
> @@ -1304,7 +1309,7 @@ int most_register_interface(struct most_interface *iface)
> iface->dev->bus = &mostbus;
> iface->dev->groups = interface_attr_groups;
> dev_set_drvdata(iface->dev, iface);
> - if (device_register(iface->dev)) {
> + if (device_add(iface->dev)) {
> dev_err(iface->dev, "Failed to register interface device\n");
> kfree(iface->p);
> put_device(iface->dev);
next prev parent reply other threads:[~2025-11-25 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 22:56 [PATCH v2 0/2] most: core: fix resource leak in most_register_interface error paths Navaneeth K
2025-11-25 22:56 ` [PATCH v2 1/2] " Navaneeth K
2025-11-25 23:10 ` Navaneeth K [this message]
2025-11-26 17:23 ` Abdun Nihaal
2025-11-25 22:56 ` [PATCH v2 2/2] most: usb: remove double cleanup of interface on registration failure Navaneeth K
2025-11-26 17:31 ` Abdun Nihaal
2025-11-26 22:08 ` Navaneeth K
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=de935747-acb4-4f08-a84e-e017b7d0f90c@gmail.com \
--to=knavaneeth786@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=parthiban.veerasooran@microchip.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;
as well as URLs for NNTP newsgroup(s).