From: Heiko Stuebner <heiko@sntech.de>
To: lee@kernel.org, jikos@kernel.org, jic23@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jdelvare@suse.com, linux@roeck-us.net,
srinivas.pandruvada@linux.intel.com, bentiss@kernel.org,
dmitry.torokhov@gmail.com, pavel@ucw.cz, ukleinek@debian.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-input@vger.kernel.org,
linux-iio@vger.kernel.org, linux-leds@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH v8 1/9] HID: hid-sensor-hub: don't use stale platform-data on remove
Date: Sun, 8 Sep 2024 23:07:55 +0200 [thread overview]
Message-ID: <20240908210803.3339919-2-heiko@sntech.de> (raw)
In-Reply-To: <20240908210803.3339919-1-heiko@sntech.de>
The hid-sensor-hub creates the individual device structs and transfers them
to the created mfd platform-devices via the platform_data in the mfd_cell.
Before commit e651a1da442a ("HID: hid-sensor-hub: Allow parallel synchronous reads")
the sensor-hub was managing access centrally, with one "completion" in the
hub's data structure, which needed to be finished on removal at the latest.
The mentioned commit then moved this central management to each hid sensor
device, resulting on a completion in each struct hid_sensor_hub_device.
The remove procedure was adapted to go through all sensor devices and
finish any pending "completion".
What this didn't take into account was, platform_device_add_data() that is
used by mfd_add{_hotplug}_devices() does a kmemdup on the submitted
platform-data. So the data the platform-device gets is a copy of the
original data, meaning that the device worked on a different completion
than what sensor_hub_remove() currently wants to access.
To fix that, use device_for_each_child() to go through each child-device
similar to how mfd_remove_devices() unregisters the devices later and
with that get the live platform_data to finalize the correct completion.
Fixes: e651a1da442a ("HID: hid-sensor-hub: Allow parallel synchronous reads")
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
drivers/hid/hid-sensor-hub.c | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/drivers/hid/hid-sensor-hub.c b/drivers/hid/hid-sensor-hub.c
index 26e93a331a51..3cd00afa453a 100644
--- a/drivers/hid/hid-sensor-hub.c
+++ b/drivers/hid/hid-sensor-hub.c
@@ -730,23 +730,30 @@ static int sensor_hub_probe(struct hid_device *hdev,
return ret;
}
+static int sensor_hub_finalize_pending_fn(struct device *dev, void *data)
+{
+ struct hid_sensor_hub_device *hsdev = dev->platform_data;
+
+ if (hsdev->pending.status)
+ complete(&hsdev->pending.ready);
+
+ return 0;
+}
+
static void sensor_hub_remove(struct hid_device *hdev)
{
struct sensor_hub_data *data = hid_get_drvdata(hdev);
unsigned long flags;
- int i;
hid_dbg(hdev, " hardware removed\n");
hid_hw_close(hdev);
hid_hw_stop(hdev);
+
spin_lock_irqsave(&data->lock, flags);
- for (i = 0; i < data->hid_sensor_client_cnt; ++i) {
- struct hid_sensor_hub_device *hsdev =
- data->hid_sensor_hub_client_devs[i].platform_data;
- if (hsdev->pending.status)
- complete(&hsdev->pending.ready);
- }
+ device_for_each_child(&hdev->dev, NULL,
+ sensor_hub_finalize_pending_fn);
spin_unlock_irqrestore(&data->lock, flags);
+
mfd_remove_devices(&hdev->dev);
mutex_destroy(&data->mutex);
}
--
2.43.0
next prev parent reply other threads:[~2024-09-08 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 21:07 [PATCH v8 0/9] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
2024-09-08 21:07 ` Heiko Stuebner [this message]
2024-10-02 13:58 ` [PATCH v8 1/9] HID: hid-sensor-hub: don't use stale platform-data on remove Lee Jones
2024-10-02 14:29 ` Benjamin Tissoires
2024-10-03 0:16 ` srinivas pandruvada
2024-09-08 21:07 ` [PATCH v8 2/9] mfd: core: make platform_data pointer const in struct mfd_cell Heiko Stuebner
2024-09-08 21:07 ` [PATCH v8 3/9] dt-bindings: mfd: add binding for qnap,ts433-mcu devices Heiko Stuebner
2024-09-08 21:07 ` [PATCH v8 4/9] mfd: add base driver for qnap-mcu devices Heiko Stuebner
2024-09-08 21:07 ` [PATCH v8 5/9] leds: add driver for LEDs from " Heiko Stuebner
2024-09-08 21:08 ` [PATCH v8 6/9] Input: add driver for the input part of " Heiko Stuebner
2024-09-08 21:08 ` [PATCH v8 7/9] hwmon: add driver for the hwmon parts " Heiko Stuebner
2024-09-08 21:08 ` [PATCH v8 8/9] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Heiko Stuebner
2024-09-08 21:08 ` [PATCH v8 9/9] arm64: dts: rockchip: set hdd led labels on qnap-ts433 Heiko Stuebner
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=20240908210803.3339919-2-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=bentiss@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=ukleinek@debian.org \
/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