summaryrefslogtreecommitdiff
path: root/Documentation/crypto/api-rng.rst
diff options
context:
space:
mode:
authorSara Sharon <sara.sharon@intel.com>2018-12-25 12:16:32 +0200
committerLuca Coelho <luciano.coelho@intel.com>2019-02-14 11:29:46 +0200
commit2ae48edcf76721d6cfcec97e5ff18cd7983b7974 (patch)
treea7a253974de112c6536ea6e9ab507a2f94f1a56d /Documentation/crypto/api-rng.rst
parent5cc9543a85ca0b721a0b3288cf2a54f3b1878f69 (diff)
iwlwifi: pcie: fix TX while flushing
When flushing TX queues no new TX should go into the system. However, in the following scenario we get TX: 1. Queues are stopped and there are packets in overflow queue 2. Station is removed and flush begins 3. Flush empties space, and reclaim path TXes SKB from overflow queue. Note that the fact the queues are stopped during the process doesn't matter - the packet will be TXed since the TX path doesn't care if TX queues are stopped or not, just if there is space in the queue, which there is, since we just freed a packet. A fix here is rather complicated, since the flow is very racy. Change code not to warn if we are TXing from overflow TX. In case there is TX from both overflow TX and TX path we will miss a warning we optimally had, but we can live with that. Make sure we don't return before overflow queue is empty, otherwise we will think queues are empty, but they will be refilled, resulting with assert. Signed-off-by: Sara Sharon <sara.sharon@intel.com> Fixes: 3955525d5d17 ("iwlwifi: pcie: buffer packets to avoid overflowing Tx queues") Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'Documentation/crypto/api-rng.rst')
0 files changed, 0 insertions, 0 deletions