summaryrefslogtreecommitdiff
path: root/certs/blacklist.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2018-12-19 18:58:35 +0300
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2019-01-02 20:05:16 +0300
commit3d433ad812baad45fa697f1af45a651147360712 (patch)
tree63aa13fe967384a1cb8eca1c2bcd1616c936f339 /certs/blacklist.c
parent6d2d0ee27c7a12371a0ca51a5db414204901228c (diff)
downloadlinux-3d433ad812baad45fa697f1af45a651147360712.tar.xz
xprtrdma: No qp_event disconnect
After thinking about this more, and auditing other kernel ULP imple- mentations, I believe that a DISCONNECT cm_event will occur after a fatal QP event. If that's the case, there's no need for an explicit disconnect in the QP event handler. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'certs/blacklist.c')
0 files changed, 0 insertions, 0 deletions