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 C93FF23C4FF; Fri, 30 May 2025 12:39:42 +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=1748608782; cv=none; b=TdVVybHh9osKnN37q2x129eAYGLeFvMXiiUVk9ur0k1FUGLPMCHEoDDxhDzCIYB7Ox/62kMOunSevSkibGrZ2gdf2DkGXLjoB2c9q3CzsrAmCHB4M4KIrAPYybKI5MdoL1fss9+bwXKdD10B24e8vpTF0pUYQMDQgeysRWDP40Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1748608782; c=relaxed/simple; bh=xg8veMOPGvIOw6WvGZ0ho8TejVo3zpsy6lpGwjyRjUQ=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=U0sy5FRnwHSND8bEb5s6eEMYej0DvaEjg/NFLdDATeaIbcZ4DeOxSPFnn6R62+UEXSiRAVXDV2vq3rOUFJYioFOl6Ias18BrkT2qkn1eJ87zguQQmXBDAsjAP58fSJKFZG6wu63GBIJ96zIreiviMyIUeiZnnx8l9daPy2DrKvs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=SqgsZPvn; 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="SqgsZPvn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 86945C4CEE9; Fri, 30 May 2025 12:39:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1748608782; bh=xg8veMOPGvIOw6WvGZ0ho8TejVo3zpsy6lpGwjyRjUQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SqgsZPvnoP/F7hHq/LEB3KWmNezkULNamF2s24LDTEs1pXa+GtSH/Y7+MaVFcVt/d DwMw5W4RKlq3i/6ABu9oVG1rMDI3crgvbwwW/ah9YGqYeOiZJexNL6AhucBvpQ7WIb 4egqcNoQ2WijmrY6PpODSH2YVN4/eS8aA1W5+KBUeAlfukxyAGKWrVXTeqM5YQ0t7d qdLUP8eQ675Me1OpFI/5ULRZmz2ycg9/JxFC2yXvIfvAL0dAuW1/oHdXb8xdGZEHoI ELRPaODnZpXxUsm+iCIfe4ly/ot5W0u8PoBI20P1ezs1HEJPsE/bI3StB0yOm49rTa Qse0Bvgc3uQ9w== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Krzysztof Kozlowski , Sebastian Reichel , Sasha Levin , sre@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH AUTOSEL 6.14 06/28] power: supply: collie: Fix wakeup source leaks on device unbind Date: Fri, 30 May 2025 08:39:12 -0400 Message-Id: <20250530123934.2574748-6-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250530123934.2574748-1-sashal@kernel.org> References: <20250530123934.2574748-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.14.9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Krzysztof Kozlowski [ Upstream commit c73d19f89cb03c43abbbfa3b9caa1b8fc719764c ] 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/20250406202730.55096-1-krzysztof.kozlowski@linaro.org Signed-off-by: Sebastian Reichel Signed-off-by: Sasha Levin --- Perfect! This confirms the pattern. Now let me analyze the commit: **YES** This commit should be backported to stable kernel trees. Here's my extensive analysis: ## Justification for Backporting ### 1. **Bug Fix Nature** The commit fixes a resource leak bug where wakeup sources are not properly cleaned up when the device is unbound. This is a clear bug fix that affects system resource management. ### 2. **Matching Pattern with Similar Commits** This commit follows the exact same pattern as the similar commits marked "YES" for backporting: - **Similar Commit #1 (gpio: mpc8xxx)** and **Similar Commit #3 (gpio: zynq)** both have identical commit messages and fix the same type of wakeup source leak by adding `device_init_wakeup(&pdev->dev, 0)` in the remove function. - All these commits are from the same author (Krzysztof Kozlowski) and have `Cc: stable@vger.kernel.org` in their commit messages, indicating explicit intention for stable tree inclusion. ### 3. **Code Analysis** The code change is minimal and surgical: - **Single line addition**: `device_init_wakeup(&ucb->dev, 0);` in the `collie_bat_remove()` function - **Proper cleanup ordering**: The line is added at the beginning of the remove function, which is the correct place for resource cleanup - **Symmetric operation**: The probe function calls `device_init_wakeup(&ucb->dev, 1)` at line 414, and now the remove function properly disables it with `device_init_wakeup(&ucb->dev, 0)` ### 4. **Resource Leak Prevention** From examining the kernel tree, I can see that: - The probe function enables wakeup with `device_init_wakeup(&ucb->dev, 1)` - Without this fix, when the driver is unbound, the wakeup source memory is leaked - This follows the established pattern seen in other drivers like gpio-zynq.c where `device_init_wakeup(&pdev->dev, 0)` is called in remove functions ### 5. **Low Risk Assessment** - **Minimal scope**: Only affects the collie battery driver cleanup path - **No functional changes**: Doesn't change driver behavior, only fixes resource cleanup - **No architectural changes**: Single line addition for proper resource management - **No new features**: Pure bug fix ### 6. **Stable Tree Criteria Compliance** - ✅ **Important bug fix**: Prevents resource leaks - ✅ **Minimal risk**: Single line, well-understood API call - ✅ **No new features**: Only fixes cleanup - ✅ **Small and contained**: Confined to one driver's remove function - ✅ **Clear side effects**: Only positive effect of proper resource cleanup ### 7. **Explicit Stable Tree Intent** The commit message doesn't include `Cc: stable@vger.kernel.org`, but the similar commits #1 and #3 from the same author fixing identical issues do have this tag, suggesting this is part of a series addressing wakeup source leaks across multiple drivers. The fix is essential for proper resource management and follows established kernel patterns for wakeup source cleanup during device unbinding. drivers/power/supply/collie_battery.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/power/supply/collie_battery.c b/drivers/power/supply/collie_battery.c index 68390bd1004f0..3daf7befc0bf6 100644 --- a/drivers/power/supply/collie_battery.c +++ b/drivers/power/supply/collie_battery.c @@ -440,6 +440,7 @@ static int collie_bat_probe(struct ucb1x00_dev *dev) static void collie_bat_remove(struct ucb1x00_dev *dev) { + device_init_wakeup(&ucb->dev, 0); free_irq(gpiod_to_irq(collie_bat_main.gpio_full), &collie_bat_main); power_supply_unregister(collie_bat_bu.psy); power_supply_unregister(collie_bat_main.psy); -- 2.39.5