Back to bug 2015205

Who When What Removed Added
Neha Ojha 2021-10-18 16:02:10 UTC Priority unspecified high
Link ID Github ceph/ceph/pull/43548
Target Release 5.2 5.1
Status NEW ASSIGNED
Assignee nojha rzarzyns
Red Hat One Jira (issues.redhat.com) 2021-10-18 16:03:01 UTC Link ID Red Hat Issue Tracker RHCEPH-2064
Neha Ojha 2021-10-26 21:06:09 UTC Status ASSIGNED POST
Veera Raghava Reddy 2021-10-27 04:24:53 UTC Fixed In Version ceph-16.2.6-14.el8cp
Status POST MODIFIED
CC tserlin
Flags needinfo?(ceph-qe-bugs)
CC ceph-qe-bugs
CC vereddy
Flags needinfo?(ceph-qe-bugs)
errata-xmlrpc 2021-10-27 04:29:10 UTC Status MODIFIED ON_QA
Pawan 2021-12-07 04:05:55 UTC Flags needinfo?(rzarzyns)
Radoslaw Zarzynski 2021-12-15 10:24:41 UTC CC skanta
QA Contact pdhiran tmathew
Flags needinfo?(rzarzyns)
Aron Gunn 2022-01-19 22:11:48 UTC Blocks 2031073
CC agunn
Aron Gunn 2022-01-26 20:31:25 UTC Docs Contact agunn
Flags needinfo?(rzarzyns)
Tintu Mathew 2022-02-03 10:56:12 UTC Status ON_QA VERIFIED
Radoslaw Zarzynski 2022-02-04 11:09:32 UTC Doc Text Cause: A ceph messenger instance maintains an internal registry of connections which can be accessed from multiple threads. Those multi-threaded accesses require proper synchronization. Unfortunately, when a connection is being unregistered (as a result of e.g. disconnect), an unsynchronized access may happen.

Consequence: A crash of messenger's user (e.g. an OSD daemon) can happen.

Fix: Proper synchronization has been implemented at the unregister stage has been implemented.

Result:
Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(rzarzyns)
Radoslaw Zarzynski 2022-02-04 11:15:46 UTC Doc Text Cause: A ceph messenger instance maintains an internal registry of connections which can be accessed from multiple threads. Those multi-threaded accesses require proper synchronization. Unfortunately, when a connection is being unregistered (as a result of e.g. disconnect), an unsynchronized access may happen.

Consequence: A crash of messenger's user (e.g. an OSD daemon) can happen.

Fix: Proper synchronization has been implemented at the unregister stage has been implemented.

Result:
Cause: A ceph messenger instance maintains an internal registry of connections which can be accessed from multiple threads. Those multi-threaded accesses require proper synchronization. Unfortunately, when a connection is being unregistered (as a result of e.g. disconnect), an unsynchronized access may happen.

Consequence: A crash of messenger's user (e.g. an OSD daemon) can happen.

Fix: Proper synchronization has been implemented at the unregister stage has been implemented.

Result: no crash (due to lack of synchronization at the connection unregister stage) is expected.
Ranjini M N 2022-02-16 06:01:59 UTC Doc Text Cause: A ceph messenger instance maintains an internal registry of connections which can be accessed from multiple threads. Those multi-threaded accesses require proper synchronization. Unfortunately, when a connection is being unregistered (as a result of e.g. disconnect), an unsynchronized access may happen.

Consequence: A crash of messenger's user (e.g. an OSD daemon) can happen.

Fix: Proper synchronization has been implemented at the unregister stage has been implemented.

Result: no crash (due to lack of synchronization at the connection unregister stage) is expected.
.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.
CC rmandyam
Flags needinfo?(rzarzyns)
Radoslaw Zarzynski 2022-02-21 11:40:46 UTC Flags needinfo?(rzarzyns)
Aron Gunn 2022-02-21 17:39:21 UTC Docs Contact agunn rmandyam
errata-xmlrpc 2022-04-04 08:02:55 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-04-04 10:22:04 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2022-04-04 10:22:04 UTC
errata-xmlrpc 2022-04-04 10:22:29 UTC Link ID Red Hat Product Errata RHSA-2022:1174

Back to bug 2015205