-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
net: openthread: rpc: Align input line buffer with openthread config #18852
Closed
lmaciejonczyk
wants to merge
1
commit into
nrfconnect:main
from
lmaciejonczyk:luma/ot_rpc_input_line
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,10 +68,14 @@ NRF_RPC_CBOR_CMD_DECODER(ot_group, ot_rpc_cmd_cli_init, OT_RPC_CMD_CLI_INIT, ot_ | |
static void ot_rpc_cmd_cli_input_line(const struct nrf_rpc_group *group, | ||
struct nrf_rpc_cbor_ctx *ctx, void *handler_data) | ||
{ | ||
char input_line_buffer[256]; | ||
struct nrf_rpc_cbor_ctx rsp_ctx; | ||
char *result; | ||
|
||
#if CONFIG_OPENTHREAD_CLI_MAX_LINE_LENGTH > 256 | ||
static | ||
#endif | ||
char input_line_buffer[CONFIG_OPENTHREAD_CLI_MAX_LINE_LENGTH - 1]; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why |
||
|
||
/* Parse the input */ | ||
result = nrf_rpc_decode_str(ctx, input_line_buffer, sizeof(input_line_buffer)); | ||
|
||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't it be allocated from heap instead?
This fix seems like we want to avoid memory misconfiguration.
@Damian-Nordic, opinions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be cleaner to use a single solution regardless of the configured max line length. Using malloc may be a better option not to increase the static RAM usage (we don't have so much unused RAM on nRF54L in this project). There's another option to just add a null-terminator in the received packet and not copy anything but this would require removing the usage of
nrf_rpc_decode_str
and perhaps adding another helper, so we can now stick to malloc and optimize it later.