Bug #40588
closed
mimic: mds: msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session
Added by shen hang almost 5 years ago.
Updated over 4 years ago.
Description
in the function handle_client_reconnect
Session *session = mds->get_session(m);
if (!session)
return;
msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session.
- Status changed from New to Fix Under Review
- Backport set to luminous
- Pull request ID set to 28796
- Assignee set to shen hang
- Start date deleted (
06/30/2019)
- Affected Versions v12.2.13 added
- Subject changed from msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session to mimic:mds: msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #40807: luminous: mds: msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session added
- Related to Bug #39026: mds: crash during mds restart added
- Related to deleted (Backport #39191: luminous: mds: crash during mds restart)
- Subject changed from mimic:mds: msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session to mimic: mds: msg weren't destroyed before handle_client_reconnect returned, if the reconnect msg was from non-existent session
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF