inotail.git - inotify enhanced tail

summary refs log tree commit diff

Branch	Commit message	Author	Age
followname	Lost in the merge	Tobias Klauser	15 years
master	Dynamically allocate inotify read buffer	Tobias Klauser	13 years
pipe	Revert "inotail.c: Decrement n_units before calling tail_pipe_from_begin"	Tobias Klauser	16 years

Tag	Download	Author	Age
v0.5	commit a9b1b5e00a...	Tobias Klauser	17 years
v0.4	commit 30282557d1...	Tobias Klauser	17 years
v0.3	commit aa67658f45...	Tobias Klauser	17 years
v0.2	commit 5d87c405cc...	Tobias Klauser	17 years
v0.1	commit d5433918e5...	Tobias Klauser	18 years

request. ->peer sends MPA_START response. ->local side ingress cpl thread begins processing the MPA_START response, but before it changes the state from MPA_REQ_SENT to FPDU_MODE: ->peer sends a RST which results in a ABORT_REQ_RSS. This triggers peer_abort_intr() which sees the state in MPA_REQ_SENT and since mpa_rev is 2, it will avoid waking up the endpoint with -ECONNRESET, assuming the stack will re-attempt the connection using MPAv1. ->Meanwhile, the cpl thread moves the state to FPDU_MODE and calls c4iw_modify_rc_qp() which calls rdma_init() which sends a RI_WR/INIT WR to firmware. But since HW sent an abort, FW correctly drops the RI_WR/INIT WR. ->So the cpl thread is stuck waiting for a reply and cannot process the ABORT_REQ_RSS cpl sitting in its input queue. Thus everything comes to a halt because no more ingress cpls are processed by the stack... The correct fix for the issue is to always do the wake up in c4iw_abort_intr() but reinitialize the wait object in c4iw_reconnect(). Fixes: 7c0a33d61187a ("RDMA/cxgb4: Don't wakeup threads for MPAv2") Signed-off-by: Steve Wise <swise@opengridcomputing.com> Signed-off-by: Hariprasad Shenai <hariprasad@chelsio.com> Signed-off-by: Doug Ledford <dledford@redhat.com>

Diffstat