FIX Kernel panic if cameras are not attached to the board #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When cameras are not attached to the board, but defined in the dts, the max9286 driver writes a debug message like:
[ 5.404743] max9286 0-0048: link0 MAX96705 at 0x0 not found: timeout GMSL link establish retries=100
This message is created concatenating a
sprintf(timeout_str, "retries=%d", priv->timeout - timeout);
with the rest of the message. The issue here is thattimeout_str
is defined as a10
char array butretries=100
is11
chars long. Plussprintf
is used while the safestsnprintf
should be preferred.This off-by-two bug is causing the following kernel panic:
Signed-off-by: Andrea Tomassetti [email protected]