Bug 2015205
| Summary: | msgr/async: fix unsafe access in unregister_conn() | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Neha Ojha <nojha> |
| Component: | RADOS | Assignee: | Radoslaw Zarzynski <rzarzyns> |
| Status: | CLOSED ERRATA | QA Contact: | Tintu Mathew <tmathew> |
| Severity: | high | Docs Contact: | Ranjini M N <rmandyam> |
| Priority: | high | ||
| Version: | 5.0 | CC: | agunn, akupczyk, bhubbard, ceph-eng-bugs, ceph-qe-bugs, nojha, rmandyam, rzarzyns, skanta, sseshasa, tserlin, vereddy, vumrao |
| Target Milestone: | --- | ||
| Target Release: | 5.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.6-14.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.No crash is expected when using the Ceph messenger instance during disconnection
A Ceph messenger instance maintains an internal registry of connections that can be accessed from multiple threads. These multi-threaded accesses require proper synchronization.
Previously, when a connection was being unregistered, for example, disconnected, unsynchronized access would happen to result in the crash of the messenger’s user, such as a Ceph OSD daemon.
This release implements proper synchronization at the unregister stage and therefore, no crashes are expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-04-04 10:22:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2031073 | ||
|
Description
Neha Ojha
2021-10-18 16:00:29 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage 5.1 Security, Enhancement, and Bug Fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:1174 |