From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793817582; b=mt0iF7YoS9MYEFyLnMcz9PlFNHAAG38zH1wHM+W+iaOipt7zn/XK68gfB9w5JOGj9zIE hXscYdL+L1YzXYhyKpBziVyVXavcdxIL4x2hjFeU3UxTYvHOuJLPSudGdH1AbTVKqlz+N BPb/dNTVprbWdoFgW6kJ74PI8qDkn/3dyKz/GfjClse2AT26LXXUDQc4n4KIm39WMvilQ ygC1FVQlvV1bT0HA/5HZaGBa6oJQT2B+p4IlZgS9omizEIcpqDECK8116skeTTaMD7Rhy EhctVLfF+bKAfxija8ja8Gmur+V5+FjotVXb5d+SVSH+4ZLuoqyxWHz1BcJeKlRfF+w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793817582; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=DvMLxBlki3uUbmQZYCI/NfK/V+8RiWix7z0CnkehUbs=; b=BRtPMzglKfH1QI/FgIKmsC6nsJ81Aci6kKYhqgQxGJ8qnYHDHpf3jE0bQz1kyTCpWpjR DxbnlBuwqYxdTSjNRe53b463Wq4W5QtYaCDcYMjF/lqvCp4FYNOiL3WElK59p/sTcfaFs JcmMYqmDVhufGg2MxJ8ZvIZOsx/2NAGSI7or2XZ5R8PBxjqlQaxor7kiVexoZvXgZWL0n Ajj+v4vND6SF44wRETdpWBqSsumxcOdphxekyksk4VUjrsDfCpHBZ5KBzBddT1qpvAZpG p5MWJCOQyck3KoShs08G7/QAZiQ4UCJBCdCvvkLtXms9jRLcnj8Zs5pEylK+NBnsIGg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=FfOz0h8j; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F039D606A326; Wed, 4 Nov 2026 18:39:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=FfOz0h8j Received: by smtp.kernel.org (Postfix) with ESMTPSA id 03F0A1F000C1; Wed, 4 Nov 2026 18:39:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1793817581; bh=DvMLxBlki3uUbmQZYCI/NfK/V+8RiWix7z0CnkehUbs=; h=From:To:Cc:Subject:Date; b=FfOz0h8j7+c5jdDl0qlPLn+rjYEsk9YbPY12IrLApeLRDyhKKzxQUB2rOWoPur159 FLvsw7SkILA1nxPAIFBTONB5wAb9UsX1Oeoqhdi2JRNs6E95GKe8NzfY1pyQoxFcZb suyRDGRXDfFlGE3SqjfMDygY8vlsGqzCc+w9MlVMAhpqyVAHYB7rTFWUXmcNi3Vnwk 2RNv/hejcuroPRYs1+fRrb9hI1x6K0EjJF12WWBcRxX8FLBAxinh0ThAcxnZ/9Vf9U pyN4SuSPQvEZpmp3YB1sZA9+ef4TZg9hLfAUvPBebJh/uRA7o/38cM0QJkL8Qx+1e+ ci07bbneOFDuQ== From: Lee Jones To: lee@kernel.org Cc: linux-kernel@vger.kernel.org, Andrew Morton , Bjorn Andersson , Daniel Jeong , Daniel Thompson , David Heidelberg , dri-devel@lists.freedesktop.org, Helge Deller , Jingoo Han , Jin Park , Kiran Gunda , Konrad Dybcio , LDD MLP , linux-arm-msm@vger.kernel.org, linux-fbdev@vger.kernel.org, Samuel Ortiz , Subbaraman Narayanamurthy Subject: [PATCH 0/6] backlight: Fix Critical and High issues reported by Sashiko Date: Wed, 4 Nov 2026 18:39:01 +0000 Message-ID: <20261104183935.1214630-1-lee@kernel.org> X-Mailer: git-send-email 2.56.0.398.g882cbad275-goog X-Mailing-List: linux-fbdev@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit These issues were reported by Sashiko. This series resolves the open Critical and High severity bug reports identified by the Sashiko AI analysis tool (https://sashiko.dev) across the Backlight subsystem: 1. lm3630a_bl: Prevent a NULL pointer dereference in lm3630a_pwm_ctrl() when PWM mode is enabled by requesting the PWM device before registering the backlight device. 2. aat2870_bl: Prevent a NULL pointer dereference on platform_get_drvdata() during devm_backlight_device_register() by populating driver data and scaling the initial brightness beforehand. 3. qcom-wled: Cancel wled->ovp_work on probe failure via devm_delayed_work_autocancel() so a scheduled OVP work item cannot fire after devm_kzalloc() frees struct wled. 4. qcom-wled: Manage wled->lock via devm_mutex_init() and remove wled_remove() so devres unwinds the backlight device, threaded IRQs, delayed work, and mutex in strict reverse registration order without calling disable_irq() on unconfigured negative or zero IRQ numbers. 5. qcom-wled: Guard against calling a NULL wled->wled_auto_detection_required() callback on WLED3 hardware when an OVP fault interrupt fires. 6. qcom-wled: Avoid an AB-BA deadlock between wled->lock and the threaded OVP IRQ handler by using disable_irq_nosync() in wled_module_enable() and verifying under wled->lock that the module remains enabled before running wled_auto_string_detection(). Cc: Andrew Morton Cc: Bjorn Andersson Cc: Daniel Jeong Cc: Daniel Thompson Cc: David Heidelberg Cc: dri-devel@lists.freedesktop.org Cc: Helge Deller Cc: Jingoo Han Cc: Jin Park Cc: Kiran Gunda Cc: Konrad Dybcio Cc: LDD MLP Cc: linux-arm-msm@vger.kernel.org Cc: linux-fbdev@vger.kernel.org Cc: Samuel Ortiz Cc: Subbaraman Narayanamurthy Lee Jones (6): backlight: lm3630a: Request PWM device before registering backlight backlight: aat2870: Initialise driver data before registering backlight backlight: qcom-wled: Cancel delayed work on probe failure backlight: qcom-wled: Manage teardown via devres and remove wled_remove() backlight: qcom-wled: Check for auto-detection callback in wled_ovp_irq_handler() backlight: qcom-wled: Avoid AB-BA deadlock in wled_module_enable() drivers/video/backlight/aat2870_bl.c | 43 +++++++++++++------------ drivers/video/backlight/lm3630a_bl.c | 12 +++---- drivers/video/backlight/qcom-wled.c | 47 +++++++++++++++------------- 3 files changed, 52 insertions(+), 50 deletions(-) -- 2.56.0.385.gac671c819a-goog