From: Hans de Goede <hansg@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: Richard Davies <richard@arachsys.com>,
Mathias Gottschlag <mgottschlag@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: focaltech - use signed coordinates to prevent underflow
Date: Sat, 8 Aug 2026 15:39:16 +0200 [thread overview]
Message-ID: <704af23d-32a7-48b6-bd3c-f7f471e18073@kernel.org> (raw)
In-Reply-To: <am_tH_F938rK6ask@google.com>
Hi,
On 3-Aug-26 03:22, Dmitry Torokhov wrote:
> focaltech_finger_state stores finger coordinates x and y as unsigned
> int. When processing relative packets, negative deltas can cause
> unsigned integer underflow if the finger moves past the left or bottom
> boundary of the touchpad, wrapping the coordinates to values near
> UINT_MAX.
>
> When clamping the coordinates in focaltech_report_state(), these
> underflowed values are clamped against priv->x_max / priv->y_max instead
> of 0, causing the cursor to jump erratically to the opposite edge of the
> touchpad.
>
> Change the coordinate variables and limits to signed int so that
> negative values resulting from relative movements clamp correctly to 0.
>
> Fixes: 05be1d079ec0 ("Input: psmouse - support for the FocalTech PS/2 protocol extensions")
> Reported-by: sashiko-bot@kernel.org
> Assisted-by: Antigravity:gemini-3.6-flash
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Regards,
Hans
> ---
> drivers/input/mouse/focaltech.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/input/mouse/focaltech.c b/drivers/input/mouse/focaltech.c
> index d3ad4af5aa09..c6f6540e3e29 100644
> --- a/drivers/input/mouse/focaltech.c
> +++ b/drivers/input/mouse/focaltech.c
> @@ -78,8 +78,8 @@ struct focaltech_finger_state {
> * Absolute position (from the bottom left corner) of the
> * finger.
> */
> - unsigned int x;
> - unsigned int y;
> + int x;
> + int y;
> };
>
> /*
> @@ -108,7 +108,7 @@ struct focaltech_hw_state {
> };
>
> struct focaltech_data {
> - unsigned int x_max, y_max;
> + int x_max, y_max;
> struct focaltech_hw_state state;
> };
>
> @@ -126,14 +126,14 @@ static void focaltech_report_state(struct psmouse *psmouse)
> input_mt_slot(dev, i);
> input_mt_report_slot_state(dev, MT_TOOL_FINGER, active);
> if (active) {
> - unsigned int clamped_x, clamped_y;
> + int clamped_x, clamped_y;
> /*
> * The touchpad might report invalid data, so we clamp
> * the resulting values so that we do not confuse
> * userspace.
> */
> - clamped_x = clamp(finger->x, 0U, priv->x_max);
> - clamped_y = clamp(finger->y, 0U, priv->y_max);
> + clamped_x = clamp(finger->x, 0, priv->x_max);
> + clamped_y = clamp(finger->y, 0, priv->y_max);
> input_report_abs(dev, ABS_MT_POSITION_X, clamped_x);
> input_report_abs(dev, ABS_MT_POSITION_Y,
> priv->y_max - clamped_y);
prev parent reply other threads:[~2026-08-08 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 1:22 Dmitry Torokhov
2026-08-03 13:29 ` Richard Davies
2026-08-04 5:24 ` Dmitry Torokhov
2026-08-08 13:39 ` Hans de Goede [this message]
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=704af23d-32a7-48b6-bd3c-f7f471e18073@kernel.org \
--to=hansg@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgottschlag@gmail.com \
--cc=richard@arachsys.com \
/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
all inboxes | Powered by JetHome®