FAILED: patch "[PATCH] iio: orientation: hid-sensor-rotation: add timestamp hack to" failed to apply to 6.1-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 6.1-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y
git checkout FETCH_HEAD
git cherry-pick -x 79a86a6cc3669416a21fef32d0767d39ba84b3aa
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2026040726-stained-tackle-e836@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
Possible dependencies:
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 79a86a6cc3669416a21fef32d0767d39ba84b3aa Mon Sep 17 00:00:00 2001
From: David Lechner <[email protected]>
Date: Sat, 7 Mar 2026 19:44:09 -0600
Subject: [PATCH] iio: orientation: hid-sensor-rotation: add timestamp hack to
not break userspace
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Add a hack to push two timestamps in the hid-sensor-rotation scan data to avoid breaking userspace applications that depend on the timestamp being at the incorrect location in the scan data due to unintentional misalignment in older kernels.
When this driver was written, the timestamp was in the correct location because of the way iio_compute_scan_bytes() was implemented at the time. (Samples were 24 bytes each.) Then commit 883f61653069 ("iio: buffer:
align the size of scan bytes to size of the largest element") changed the computed scan_bytes to be a different size (32 bytes), which caused iio_push_to_buffers_with_timestamp() to place the timestamp at an incorrect offset.
There have been long periods of time (6 years each) where the timestamp was in either location, so to not break either case, we open-code the timestamps to be pushed to both locations in the scan data.
drivers/iio/orientation/hid-sensor-rotation.c +19 -3
@@ -20,7 +20,12 @@ struct dev_rot_state {struct hid_sensor_hub_attribute_info quaternion;struct { IIO_DECLARE_QUATERNION(s32, sampled_vals); -aligned_s64 timestamp; +/* +* ABI regression avoidance: There are two copies of the same +* timestamp in case of userspace depending on broken alignment +* from older kernels. +*/ +aligned_s64 timestamp[2 ]; } scan;int scale_pre_decml;int scale_post_decml;
@@ -154,8 +159,19 @@ static int dev_rot_proc_event(struct hid_sensor_hub_device *hsdev,if (!rot_state->timestamp) rot_state->timestamp =iio_get_time_ns (indio_dev); -iio_push_to_buffers_with_timestamp (indio_dev, &rot_state->scan, - rot_state->timestamp); +/* +* ABI regression avoidance: IIO previously had an incorrect +* implementation of iio_push_to_buffers_with_timestamp() that +* put the timestamp in the last 8 bytes of the buffer, which +* was incorrect according to the IIO ABI. To avoid breaking +* userspace that may be depending on this broken behavior, we +* put the timestamp in both the correct place [0] and the old +* incorrect place [1]. +*/ + rot_state->scan.timestamp[0 ] = rot_state->timestamp; + rot_state->scan.timestamp[1 ] = rot_state->timestamp; + +iio_push_to_buffers (indio_dev, &rot_state->scan); rot_state->timestamp =0 ; }