[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251125225606.70719-1-knavaneeth786@gmail.com>
Date: Tue, 25 Nov 2025 22:56:04 +0000
From: Navaneeth K <knavaneeth786@...il.com>
To: parthiban.veerasooran@...rochip.com,
christian.gromm@...rochip.com,
gregkh@...uxfoundation.org
Cc: linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Navaneeth K <knavaneeth786@...il.com>
Subject: [PATCH v2 0/2] most: core: fix resource leak in most_register_interface error paths
This series fixes a resource leak in most_register_interface() where
early errors (allocation failures) would return without releasing the
device, leaking memory.
It switches to the split device_initialize() + device_add() pattern
to ensure put_device() can be safely called on all error paths.
It also updates the most_usb driver to remove manual error handling
that would otherwise cause a double-free with the new core logic.
Changes in v2:
- Replaced the previous single-driver fix ("staging: most: dim2: fix
missing cleanup...") which was NACKed because it introduced a
double-free risk.
- Moved the fix to the Core (core.c) to handle cleanup centrally via
put_device().
- Updated most_usb.c to remove conflicting manual cleanup.
- Dropped the dim2.c patch as the upstream code is already correct for
this new core logic (it relies on the release callback, which core
now triggers).
Navaneeth K (2):
most: core: fix resource leak in most_register_interface error paths
most: usb: remove double cleanup of interface on registration failure
drivers/most/core.c | 9 +++++++--
drivers/most/most_usb.c | 11 +++--------
2 files changed, 10 insertions(+), 10 deletions(-)
Powered by blists - more mailing lists