-
-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange data in logs, file_report_buffer: expected 2 bytes, but got 512
#2401
Comments
The decoding should have started earlier, with On one hand, it is indeed odd that it returns 512 bytes, using an uninitialized memory block. By content, it was memory that once belonged to the process and was since freed. So the bytes in it are not too much surprising, the length is. Code comments are about broken device report descriptors, so maybe that's just it - many vendors can't read USB specs well. |
Just some notes as I look at this superficially ;
where |
(same device and system discussed in #2399 )
looking at logs, I thought it strange that a request would return 512 bytes :
I thought some of that data looked like ASCII, so out of curiosity I ran it through
xxd -r -p | xxd -b 1
:And, it just so happens that I have this warning earlier in journalctl :
nut-driver@belk[30528]: Running as foreground process, but saving a PID file anyway
How is that text ending up in a seemingly unrelated place ?
The text was updated successfully, but these errors were encountered: