diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2026-10-11 23:12:40 -0700 |
|---|---|---|
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2026-10-19 14:35:41 -0700 |
| commit | c1d13bfdb9c75c2885d10332174a887349eb0b51 (patch) | |
| tree | e94967691790b2e9ba8c0746ccc936b41f5c9583 /scripts/Makefile.thinlto | |
| parent | 6c9063f78856d2c8ab0d395b931c635e8e71ccc5 (diff) | |
| download | linux-c1d13bfdb9c75c2885d10332174a887349eb0b51.tar.gz linux-c1d13bfdb9c75c2885d10332174a887349eb0b51.zip | |
Input: always accept EV_SYN in input_event()
Commit 0cd587735205 ("Input: preallocate memory to hold event values")
moved allocation of dev->vals into input_allocate_device(), which caused
input core to accumulate events reported while seeding initial device
state before input_register_device().
However, because EV_SYN is only set in dev->evbit during
input_register_device() (and some drivers also overwrite dev->evbit
directly before registration), any EV_SYN/SYN_REPORT events sent before
registration were dropped by is_event_supported(), leaving those seeded
events stuck in dev->vals until the next SYN_REPORT after registration.
Always accept EV_SYN in input_event() and input_inject_event() without
checking dev->evbit so input_sync() flushes dev->vals as intended.
Reported-by: Karlos Abel <kabel@voidship.net>,
Fixes: 0cd587735205 ("Input: preallocate memory to hold event values")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Acked-by: Jiri Kosina <jkosina@suse.com>
Link: https://patch.msgid.link/asx50uz6iafsyAd5@google.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
