Filter out touchscreen devices with areas that overflow.
When initialized incorrectly, some touchscreen controllers can report bogus values for their sizes. Chrome uses the touchscreen area in calculations; if that area overflows a signed 32-bit int, it check-fails. Thus, a misbehaving touchscreen can cause Chrome to crash-loop, rendering a device unusable. Mitigate this by warning about the bogus size and then ignoring the touchscreen input device. A non-functional touchscreen is better than an unusable device. BUG=b:162596241 Change-Id: I9291c176ed778f5ddb8a80d9ea75f17be7bd0554 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353973Reviewed-by:Michael Spang <spang@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#798512}
Showing
Please register or sign in to comment