diff options
author | Alex Elder <elder@inktank.com> | 2013-04-01 16:12:14 -0500 |
---|---|---|
committer | Sage Weil <sage@inktank.com> | 2013-05-01 21:17:54 -0700 |
commit | ace6d3a96f00c271b3f337adcde8e8cbe39c3820 (patch) | |
tree | cb93ac34e892b61ee9303e051384bb64ed925caa /kernel/gcov/Kconfig | |
parent | 25d71cb92d8eb48df9cbd8cc4bb28e88ee8e88d9 (diff) | |
download | linux-stable-ace6d3a96f00c271b3f337adcde8e8cbe39c3820.tar.gz linux-stable-ace6d3a96f00c271b3f337adcde8e8cbe39c3820.tar.bz2 linux-stable-ace6d3a96f00c271b3f337adcde8e8cbe39c3820.zip |
libceph: drop ceph_osd_request->r_con_filling_msg
A field in an osd request keeps track of whether a connection is
currently filling the request's reply message. This patch gets rid
of that field.
An osd request includes two messages--a request and a reply--and
they're both associated with the connection that existed to its
the target osd at the time the request was created.
An osd request can be dropped early, even when it's in flight.
And at that time both messages are released. It's possible the
reply message has been supplied to its connection to receive
an incoming response message at the time the osd request gets
dropped. So ceph_osdc_release_request() revokes that message
from the connection before releasing it so things get cleaned up
properly.
Previously this may have caused a problem, because the connection
that a message was associated with might have gone away before the
revoke request. And to avoid any problems using that connection,
the osd client held a reference to it when it supplies its response
message.
However since this commit:
38941f80 libceph: have messages point to their connection
all messages hold a reference to the connection they are associated
with whenever the connection is actively operating on the message
(i.e. while the message is queued to send or sending, and when it
data is being received into it). And if a message has no connection
associated with it, ceph_msg_revoke_incoming() won't do anything
when asked to revoke it.
As a result, there is no need to keep an additional reference to the
connection associated with a message when we hand the message to the
messenger when it calls our alloc_msg() method to receive something.
If the connection *were* operating on it, it would have its own
reference, and if not, there's no work to be done when we need to
revoke it.
So get rid of the osd request's r_con_filling_msg field.
This resolves:
http://tracker.ceph.com/issues/4647
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'kernel/gcov/Kconfig')
0 files changed, 0 insertions, 0 deletions