From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8E1D328A411; Fri, 6 Jun 2025 15:42:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749224559; cv=none; b=KmZ+uSdxdGfAOAMKV4yFacWABsTP+IR9NVFAqWfCHm6kKA9Q/f3Bh9civG5+EnpJusOV7mTUqWPipvF26CHpcll4S1ZspU1HXMb/lmXL5F8Uy8PkIekc9s7o59g0SsH8aQ4GwX2liWRGMgxPUYBMmGYEFHS3NKMIEG5khcGAPEU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749224559; c=relaxed/simple; bh=cSV2s7RixPkjrBSQuDprrXa/GlT3m+vYjOcot1cKvq8=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=Zhnbdo2EkziLf0bgrN9FSNJy7UfNXwwqpeU74DZSooEcHOL0NWRUHX2wWMp+t2lgk/f6yc8jYLzLLHl1Osu7NRN1iRHIxKD5EfXcL9MryZhIbu0q++jDOaUsL5TUXC3LXMXsA6YU679jsMomaSaFiNGl9h0FuEghNe/D8P5UGno= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LHo0E9mz; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="LHo0E9mz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2C8DDC4CEF0; Fri, 6 Jun 2025 15:42:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1749224559; bh=cSV2s7RixPkjrBSQuDprrXa/GlT3m+vYjOcot1cKvq8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=LHo0E9mzcLxlNPpzNG655U1uhglA4dziPUkJMFWeDOhfJl9ZUIUdRiBXFyiwU6Yqe zYmXhDaHcMvG224dW7ixzAYnIWUXWzmRDATJR55Gv1j82Yp8fJORgFWzqQ1gCyXU4+ SzXbioKnIhZxE+gFKdtEKURyDeuv+P039G7Qn+k1Q6FgSXGjh/L1Pho2jEzAL7fU5e eMbwRj9T7DT43nmciAvvAh/Ksdm9WSdQS49PAqb7qfxM5aComYysyewki166hNKGk3 PcV9KIrazTXlET30BWHlLigRS6CxLYc13P2OMiwdhQs90lxbmqY50DVfdlURDHFlNV wp41Dl7WVAppw== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Krzysztof Kozlowski , Lee Jones , Sasha Levin , cw00.choi@samsung.com, krzk@kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH AUTOSEL 6.14 09/19] mfd: max14577: Fix wakeup source leaks on device unbind Date: Fri, 6 Jun 2025 11:42:15 -0400 Message-Id: <20250606154225.546969-9-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250606154225.546969-1-sashal@kernel.org> References: <20250606154225.546969-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.14.10 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Krzysztof Kozlowski [ Upstream commit d905d06e64b0eb3da43af6186c132f5282197998 ] Device can be unbound, so driver must also release memory for the wakeup source. Signed-off-by: Krzysztof Kozlowski Link: https://lore.kernel.org/r/20250406-mfd-device-wakekup-leak-v1-3-318e14bdba0a@linaro.org Signed-off-by: Lee Jones Signed-off-by: Sasha Levin --- Now let me understand the difference between the fixes - the historical commits show two patterns: 1. Using `devm_device_init_wakeup()` - automatically handles cleanup 2. Manual cleanup by calling `device_init_wakeup(dev, false)` in remove functions Let me check if this specific commit has `Cc: stable@vger.kernel.org` in the message: Based on my analysis of this commit and comparison with the similar historical commits, here is my assessment: **YES** This commit should be backported to stable kernel trees for the following reasons: ## Analysis ### **Code Change Analysis** The commit adds a single line in the `max14577_i2c_remove()` function: ```c + device_init_wakeup(max14577->dev, false); ``` This addition occurs at drivers/mfd/max14577.c:459, right before `mfd_remove_devices()` is called. ### **Bug Fix Characteristics** 1. **Memory Leak Fix**: The commit fixes a wakeup source memory leak that occurs when the device is unbound. When `device_init_wakeup(dev, true)` is called during probe (line 442), it allocates memory for wakeup source structures. Without the corresponding cleanup call, this memory is leaked on device removal. 2. **Small and Contained**: The fix is minimal - a single line addition that mirrors the cleanup pattern used throughout the kernel. 3. **Low Risk**: The change has extremely low regression risk since it only adds proper cleanup that should have been there originally. ### **Comparison with Historical Similar Commits** Looking at the provided historical commits, there are two categories: **YES commits (backported)**: - `gpio: mpc8xxx: Fix wakeup source leaks on device unbind` - Same exact pattern and includes `Cc: stable@vger.kernel.org` - `gpio: zynq: Fix wakeup source leaks on device unbind` - Same exact pattern and includes `Cc: stable@vger.kernel.org` **NO commits (not backported)**: - IIO driver commits that use `devm_device_init_wakeup()` instead of manual cleanup The key difference is that the YES commits use the same fix pattern as this MFD commit - manual cleanup in the remove function, while the NO commits use the `devm_` managed approach that automatically handles cleanup. ### **Impact Assessment** - **User Impact**: Memory leaks on device unbind affect systems where MFD devices are frequently bound/unbound - **Subsystem**: MFD (Multi-Function Device) is a core kernel subsystem used by many embedded systems - **Regression Risk**: Minimal - adding proper cleanup cannot cause functional regression ### **Stable Tree Criteria Met** 1. ✅ Fixes an important bug (memory leak) 2. ✅ Small and contained change 3. ✅ No architectural changes 4. ✅ Minimal risk of regression 5. ✅ Follows established patterns seen in other backported commits The commit follows the exact same pattern as the GPIO driver commits that were successfully backported to stable trees (commits #1 and #2 in the historical examples), making it a clear candidate for backporting. drivers/mfd/max14577.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mfd/max14577.c b/drivers/mfd/max14577.c index 6fce79ec2dc64..7e7e8af9af224 100644 --- a/drivers/mfd/max14577.c +++ b/drivers/mfd/max14577.c @@ -456,6 +456,7 @@ static void max14577_i2c_remove(struct i2c_client *i2c) { struct max14577 *max14577 = i2c_get_clientdata(i2c); + device_init_wakeup(max14577->dev, false); mfd_remove_devices(max14577->dev); regmap_del_irq_chip(max14577->irq, max14577->irq_data); if (max14577->dev_type == MAXIM_DEVICE_TYPE_MAX77836) -- 2.39.5