[EN] Kernel error for Logitech wireless receiver

[GoinEasy9]

I've been getting this error during boot, although, it does not seem to be causing any problems.  I've been using a Logitech M570 wireless trackball for quite a while and it has only started appearing since the last kernel update (3.16-2).

The error: kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255

The device: Bus 011 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver

Has anyone else seen this, or, has something changed in the kernel?  The only difference I've seen is with the KDE battery monitor.  It's reading 100% for the trackball, and, I do believe the last time I looked, it was at 93%. 

[ayla]

Code: [Select]

-- Logs begin at Di 2013-12-31 15:51:44 CET, end at Di 2014-09-09 16:03:47 CEST. --
Sep 09 15:30:56 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:0
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255
Sep 09 15:31:00 neskaya kernel: logitech-djreceiver 0003:046D:C52B.0003: logi_dj_raw_event: invalid device index:255

using a logitech k750 keyboard, and a LT MX mouse. Have no problems, only looked at the journal after reading your post.

greets
ayla

[GoinEasy9]

Thanks for the post ayla.  I guess I'm not alone.  I wonder what changed?

[GoinEasy9]

I just found this on the kernel mailing list.  It seems to be a solution for the problem. At least I think it does.

http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg723365.html

Quote from the post:

device_index is a char type and the size of paired_dj_deivces is 7 elements, therefore proper bounds checking has to be applied to device_index before it is used.

We are currently performing the bounds checking in logi_dj_recv_add_djhid_device(), which is too late, as malicious device could send REPORT_TYPE_NOTIF_DEVICE_UNPAIRED early enough and trigger the problem in one of the report forwarding functions called from logi_dj_raw_event().

This was just posted today 9/11/14, so, I guess we'll see the fix eventually.