diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2017-10-27 10:49:51 -0400 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2017-11-07 16:44:02 -0500 |
| commit | 77a08867a66796f8316449e030e0bfc84f2a3f66 (patch) | |
| tree | 6b6155101bd0462b3fae131576a4080a79b7df8b /kernel/futex_compat.c | |
| parent | 7e981a8afa6d8d1d93e2b3d162aa81cc7b537208 (diff) | |
svcrdma: Enqueue after setting XPT_CLOSE in completion handlers
I noticed the server was sometimes not closing the connection after
a flushed Send. For example, if the client responds with an RNR NAK
to a Reply from the server, that client might be deadlocked, and
thus wouldn't send any more traffic. Thus the server wouldn't have
any opportunity to notice the XPT_CLOSE bit has been set.
Enqueue the transport so that svcxprt notices the bit even if there
is no more transport activity after a flushed completion, QP access
error, or device removal event.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-By: Devesh Sharma <devesh.sharma@broadcom.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'kernel/futex_compat.c')
0 files changed, 0 insertions, 0 deletions