-
Notifications
You must be signed in to change notification settings - Fork 304
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
DAOS-16251 tests: Fix various memory issues #15147
Conversation
This patch fixes the following memory issues in daos_test: - IO13 (basic_byte_array) may read beyond the end of buf_out. - REBUILD6 (rebuild_snap_update_recs) may write beyond the end of string. - ARRAY19 (test_async_io) may write beyond the end of dkey_str[]. - daos_start_server can't just increment svc->rl_nr without making sure that svc->rl_ranks matches svc->rl_nr. Signed-off-by: Li Wei <[email protected]> Required-githooks: true DAOS-16251 tests: Fix EC2 use-after-scope Signed-off-by: Li Wei <[email protected]> Required-githooks: true
Ticket title is 'DAOS 2.4.2-4: Errored DAOS engine 0 exited unexpectedly on daos_user' |
03d1555
to
3d079e6
Compare
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.
Over all seems good to me.
Just some minor details.
Signed-off-by: Li Wei <[email protected]> Required-githooks: true
Required-githooks: true
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.
LGTM
This patch fixes the following memory issues in daos_test:
IO13 (basic_byte_array) may read beyond the end of buf_out.
REBUILD6 (rebuild_snap_update_recs) may write beyond the end of
string.
ARRAY19 (test_async_io) may write beyond the end of dkey_str[].
daos_start_server can't just increment svc->rl_nr without making
sure that svc->rl_ranks matches svc->rl_nr.
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: