Skip to content

[23847] Protect DataReaderInstance alive_writers attribute (backport #6123)#6158

Merged
MiguelCompany merged 1 commit into3.3.xfrom
mergify/bp/3.3.x/pr-6123
Nov 7, 2025
Merged

[23847] Protect DataReaderInstance alive_writers attribute (backport #6123)#6158
MiguelCompany merged 1 commit into3.3.xfrom
mergify/bp/3.3.x/pr-6123

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 6, 2025

Description

This PR attempts to solve the data race produced in intraprocess scenario, when a writer sends a message from a thread (which updates its associated instance state in the reader receiving the message: DataReaderImpl::on_new_cache_change_added → DataReaderHistory::update_instance_nts → … → DataReaderInstance::writer_set), while from another thread the instances state of the same reader is also updated without protection (e.g., when destroying a matched writer: DataReaderImpl::update_subscription_matched_status → … → DataReaderInstance::writer_unregister). In the first thread the reader mutex is taken before calling update_instance_nts, the problem is that in the second thread that mutex is never taken.

@Mergifyio backport 3.3.x 3.2.x 2.14.x

Contributor Checklist

  • Commit messages follow the project guidelines.

  • The code follows the style guidelines of this project.

  • Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally

  • N/A Any new/modified methods have been properly documented using Doxygen.

  • N/A Any new configuration API has an equivalent XML API (with the corresponding XSD extension)

  • Changes are backport compatible: they do NOT break ABI nor change library core behavior.

  • Changes are API compatible.

  • N/A New feature has been added to the versions.md file (if applicable).

  • N/A New feature has been documented/Current behavior is correctly described in the documentation.

  • Applicable backports have been included in the description.

Reviewer Checklist

  • The PR has a milestone assigned.
  • The title and description correctly express the PR's purpose.
  • Check contributor checklist is correct.
  • If this is a critical bug fix, backports to the critical-only supported branches have been requested.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

This is an automatic backport of pull request #6123 done by [Mergify](https://mergify.com).

Signed-off-by: Juan Lopez Fernandez <juanlopez@eprosima.com>
(cherry picked from commit 19d6a2b)
@MiguelCompany MiguelCompany added this to the v3.3.1 milestone Nov 6, 2025
@MiguelCompany MiguelCompany self-requested a review November 6, 2025 10:09
@github-actions github-actions bot added the ci-pending PR which CI is running label Nov 6, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Nov 6, 2025

🧪 CI Insights

Here's what we observed from your CI run for 57958fb.

❌ Job Failures

Pipeline Job Health on 3.3.x Retries 🔍 CI Insights 📄 Logs
Fast DDS MacOS CI mac-ci / fastdds_test () Unknown 0 View View
Fast DDS Windows CI windows-ci / fastdds_test (RelWithDebInfo, examples), v142 Unknown 0 View View
windows-ci / fastdds_test (RelWithDebInfo, examples), v143 Unknown 0 View View

@MiguelCompany MiguelCompany merged commit 9717a4e into 3.3.x Nov 7, 2025
25 of 28 checks passed
@MiguelCompany MiguelCompany deleted the mergify/bp/3.3.x/pr-6123 branch November 7, 2025 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-pending PR which CI is running

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants