Skip to content

DAOS-19495 object: fix segfault on max epoch query in a transaction (… - #18890

Open
mchaarawi wants to merge 1 commit into
release/2.8from
mschaara/19495-2.8
Open

DAOS-19495 object: fix segfault on max epoch query in a transaction (…#18890
mchaarawi wants to merge 1 commit into
release/2.8from
mschaara/19495-2.8

Conversation

@mchaarawi

Copy link
Copy Markdown
Contributor

#18858)

daos_obj_query_max_epoch() has neither dkey nor akey, but dc_tx_attach() cached it as a read with nr=1, so dc_tx_add_read() left dcsr_nr=1 while dcr_iods stayed NULL. The commit then crashed dereferencing dcr_iods in dc_tx_cpd_sub_reqs_size(). Record it as an object level read (nr=0) and force nr=0 whenever no dkey is given. Add DTX42 regression test.

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

…18858)

daos_obj_query_max_epoch() has neither dkey nor akey, but dc_tx_attach()
cached it as a read with nr=1, so dc_tx_add_read() left dcsr_nr=1 while
dcr_iods stayed NULL. The commit then crashed dereferencing dcr_iods in
dc_tx_cpd_sub_reqs_size(). Record it as an object level read (nr=0) and
force nr=0 whenever no dkey is given. Add DTX42 regression test.

Signed-off-by: Mohamad Chaarawi <mohamad.chaarawi@hpe.com>
@mchaarawi mchaarawi added the clean-cherry-pick Cherry-pick from another branch that did not require additional edits label Aug 19, 2026
@github-actions

Copy link
Copy Markdown

Ticket title is 'SEGV seen in DTX operation involving daos_obj_query_max_epoch'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-19495

@github-actions github-actions Bot added the priority Ticket has high priority (automatically managed) label Aug 19, 2026
@mchaarawi
mchaarawi marked this pull request as ready for review August 20, 2026 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clean-cherry-pick Cherry-pick from another branch that did not require additional edits priority Ticket has high priority (automatically managed)

Development

Successfully merging this pull request may close these issues.

1 participant