diff options
| author | Russ Gorby <russ.gorby@intel.com> | 2012-08-13 13:44:40 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-07 08:35:55 -0700 |
| commit | f73fd7d132c40bb779017444da92aed6c5dfcd95 (patch) | |
| tree | 7d827d70ce1d3626d2d69a16e3d5ca0fde62cd4a /lib/mpi/mpi-scan.c | |
| parent | fc8cb6c219bf26cb4712f7daf8e1096030e5d0c9 (diff) | |
n_gsm: added interlocking for gsm_data_lock for certain code paths
commit 5e44708f75b0f8712da715d6babb0c21089b2317 upstream.
There were some locking holes in the management of the MUX's
message queue for 2 code paths:
1) gsmld_write_wakeup
2) receipt of CMD_FCON flow-control message
In both cases gsm_data_kick is called w/o locking so it can collide
with other other instances of gsm_data_kick (pulling messages tx_tail)
or potentially other instances of __gsm_data_queu (adding messages to tx_head)
Changed to take the tx_lock in these 2 cases
Signed-off-by: Russ Gorby <russ.gorby@intel.com>
Tested-by: Yin, Fengwei <fengwei.yin@intel.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/mpi/mpi-scan.c')
0 files changed, 0 insertions, 0 deletions