summaryrefslogtreecommitdiffstats
path: root/samples/user_events
diff options
context:
space:
mode:
authorNiels Dossche <dossche.niels@gmail.com>2022-02-28 17:53:30 +0100
committerJason Gunthorpe <jgg@nvidia.com>2022-04-04 19:45:02 +0200
commit4d809f69695d4e7d1378b3a072fa9aef23123018 (patch)
treea3292f1cb804d46dbd39a9303a75eee194c28f12 /samples/user_events
parentIB/cm: Cancel mad on the DREQ event when the state is MRA_REP_RCVD (diff)
downloadlinux-4d809f69695d4e7d1378b3a072fa9aef23123018.tar.xz
linux-4d809f69695d4e7d1378b3a072fa9aef23123018.zip
IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition
The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition. Fixes: d757c60eca9b ("IB/rdmavt: Fix concurrency panics in QP post_send and modify to error") Link: https://lore.kernel.org/r/20220228165330.41546-1-dossche.niels@gmail.com Signed-off-by: Niels Dossche <dossche.niels@gmail.com> Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'samples/user_events')
0 files changed, 0 insertions, 0 deletions