https://bugs.winehq.org/show_bug.cgi?id=51828
Ivo Ivanov logos128@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Ivo Ivanov logos128@gmail.com --- (In reply to Rémi Bernon from comment #2)
Thanks, I sent some updated patches to fix this too (https://source.winehq.org/patches/data/216075, https://source.winehq.org/patches/data/216074, https://source.winehq.org/patches/data/216076).
Indeed this is much more complete solution. I can confirm that everything works properly now, the reports get through the check as expected. Tested with 5a8dcb062793fbb68997e1b54ebc2666a2b2834d from yesterday.
Note that the unit tests show that reports *must* be dropped when their size is invalid.
But, like for the reports coming from user-space, it most likely checks that the report length matches the declaration for the report id, which is what I implemented.
Do the unit tests reflect the behavior on Windows? Just trying to understand better the tests creation process.