Skip to content
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

Fix double-locking issue in DataSharingListener (backport #5468) #5521

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 20, 2024

Description

In the run() function of DataSharingListener, due to time jumps, the wait() function may occasionally experience spurious wakeups and throw a const boost::interprocess_exception. After executing continue in the catch block, the code attempts to lock the mutex again while it's already locked, which leads to a std::system_error exception being thrown(e.what(): Resource deadlock avoided), ultimately causing the program to crash.

图片1

未命名文件 (5)

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.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.
  • N/A: 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 #5468 done by [Mergify](https://mergify.com).

@MiguelCompany MiguelCompany added this to the v3.0.2 milestone Dec 20, 2024
@Mario-DL Mario-DL requested review from Mario-DL and removed request for Mario-DL December 23, 2024 06:58
@github-actions github-actions bot added the ci-pending PR which CI is running label Dec 23, 2024
@Mario-DL
Copy link
Member

I re-run the mac ci just to ensure that the failing test is unrelated

Signed-off-by: Xiaojing Cao <xiaojing.cao@hirain.com>
(cherry picked from commit 059457a)
@Mario-DL Mario-DL force-pushed the mergify/bp/3.0.x/pr-5468 branch from 116000d to 6acc122 Compare January 21, 2025 14:25
@Mario-DL Mario-DL requested review from Mario-DL and removed request for Mario-DL January 21, 2025 14:25
Copy link
Member

@Mario-DL Mario-DL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, previous failed test in MacOS was unrelated. I rebased, run the test in my local and it was passing.

@Mario-DL Mario-DL added ready-to-merge Ready to be merged. CI and changes have been reviewed and approved. and removed ci-pending PR which CI is running labels Jan 22, 2025
@MiguelCompany MiguelCompany merged commit 859ebab into 3.0.x Jan 22, 2025
16 of 17 checks passed
@MiguelCompany MiguelCompany deleted the mergify/bp/3.0.x/pr-5468 branch January 22, 2025 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Ready to be merged. CI and changes have been reviewed and approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants