Project

General

Profile

Actions
Copy link

Bug #1985

closed

msgr: creating new Pipe for pre-existing connection leaks Pipe if they don't replace

Added by Greg Farnum about 12 years ago. Updated about 5 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
Greg Farnum
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

See #1981. Turns out that if we have an existing Pipe but don't replace it, we never clean ourselves up and we need to.

Actions
Copy link
 #1

Updated by Greg Farnum about 12 years ago

  • Status changed from New to 4

Hacked up a small patch that should do it, but need to test and get some feedback on related protocol stuff I ran into.

Actions
Copy link
 #2

Updated by Sage Weil about 12 years ago

  • Status changed from 4 to Won't Fix

at least until we demonstrate the problem (after the msg leak fix). this will probably be moot after refactoring some of this code anyway.

Actions
Copy link
 #3

Updated by Greg Farnum almost 12 years ago

I've still got this sitting around in my workspace. Since we seem to have pushed back a messenger re-do, perhaps we should bring this patch in after all?

Actions
Copy link
 #4

Updated by Greg Farnum about 5 years ago

  • Project changed from Ceph to Messengers
  • Category deleted (msgr)
  • Target version deleted (v0.42)
Actions
Copy link

Also available in: Atom PDF