diff options
| author | Niels Dossche <[email protected]> | 2022-02-28 17:53:30 +0100 |
|---|---|---|
| committer | Jason Gunthorpe <[email protected]> | 2022-04-04 14:45:02 -0300 |
| commit | 4d809f69695d4e7d1378b3a072fa9aef23123018 (patch) | |
| tree | a3292f1cb804d46dbd39a9303a75eee194c28f12 /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 107dd7beba403a363adfeb3ffe3734fe38a05cce (diff) | |
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/[email protected]
Signed-off-by: Niels Dossche <[email protected]>
Acked-by: Dennis Dalessandro <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions