diff options
author | K. Y. Srinivasan <kys@microsoft.com> | 2016-04-02 16:17:38 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-04-30 14:05:44 -0700 |
commit | 1db488d12894f1936360779d6ab2aede3dd7f06a (patch) | |
tree | 41d26d3e3e0c89a31b6f723b978ba9ac776879b3 /drivers/nvmem | |
parent | 82dc4afd7e65455464f0fc2fe6976efde54fe451 (diff) | |
download | linux-1db488d12894f1936360779d6ab2aede3dd7f06a.tar.gz linux-1db488d12894f1936360779d6ab2aede3dd7f06a.tar.bz2 linux-1db488d12894f1936360779d6ab2aede3dd7f06a.zip |
Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()
On the consumer side, we have interrupt driven flow management of the
producer. It is sufficient to base the signaling decision on the
amount of space that is available to write after the read is complete.
The current code samples the previous available space and uses this
in making the signaling decision. This state can be stale and is
unnecessary. Since the state can be stale, we end up not signaling
the host (when we should) and this can result in a hang. Fix this
problem by removing the unnecessary check. I would like to thank
Arseney Romanenko <arseneyr@microsoft.com> for pointing out this issue.
Also, issue a full memory barrier before making the signaling descision
to correctly deal with potential reordering of the write (read index)
followed by the read of pending_sz.
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
Tested-by: Dexuan Cui <decui@microsoft.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/nvmem')
0 files changed, 0 insertions, 0 deletions