summaryrefslogtreecommitdiff
path: root/net/caif/cfdbgl.c
diff options
context:
space:
mode:
authorKaike Wan <kaike.wan@intel.com>2020-02-10 08:10:26 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-02-19 19:53:05 +0100
commit327f33e54c7f70b05968c2a92dbe8b4ed9279fa9 (patch)
tree18f5787194a803e2df82705a75738ac68223ce58 /net/caif/cfdbgl.c
parente30e30c042fe6018a46275f2b62b63694c02af33 (diff)
IB/hfi1: Acquire lock to release TID entries when user file is closed
commit a70ed0f2e6262e723ae8d70accb984ba309eacc2 upstream. Each user context is allocated a certain number of RcvArray (TID) entries and these entries are managed through TID groups. These groups are put into one of three lists in each user context: tid_group_list, tid_used_list, and tid_full_list, depending on the number of used TID entries within each group. When TID packets are expected, one or more TID groups will be allocated. After the packets are received, the TID groups will be freed. Since multiple user threads may access the TID groups simultaneously, a mutex exp_mutex is used to synchronize the access. However, when the user file is closed, it tries to release all TID groups without acquiring the mutex first, which risks a race condition with another thread that may be releasing its TID groups, leading to data corruption. This patch addresses the issue by acquiring the mutex first before releasing the TID groups when the file is closed. Fixes: 3abb33ac6521 ("staging/hfi1: Add TID cache receive init and free funcs") Link: https://lore.kernel.org/r/20200210131026.87408.86853.stgit@awfm-01.aw.intel.com Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com> Signed-off-by: Kaike Wan <kaike.wan@intel.com> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com> Signed-off-by: Jason Gunthorpe <jgg@mellanox.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/caif/cfdbgl.c')
0 files changed, 0 insertions, 0 deletions