From: Hank Janssen on
From: Haiyang Zhang <haiyangz(a)microsoft.com>

Fixed the value of the 64bit-hole inside ring buffer, this
caused a problem on Hyper-V when running checked Windows builds.

Checked builds of Windows are used internally and given to external system
integrators at times. They are builds that for example that all elements in a
structure follow the definition of that Structure. The bug this fixed was for a
field that we did not fill in at all (Because we do Not use it on the Linux side),
and the checked build of windows gives errors on it internally to the Windows logs.

This fixes that error.

Signed-off-by:Hank Janssen <hjanssen(a)microsoft.com>
Signed-off-by:Haiyang Zhang <haiyangz(a)microsoft.com>
Cc: stable <stable(a)kernel.org>
---
drivers/staging/hv/ring_buffer.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/hv/ring_buffer.c b/drivers/staging/hv/ring_buffer.c
index 66a4974..133f909 100644
--- a/drivers/staging/hv/ring_buffer.c
+++ b/drivers/staging/hv/ring_buffer.c
@@ -192,8 +192,7 @@ Description:
static inline u64
GetRingBufferIndices(RING_BUFFER_INFO *RingInfo) {
- return ((u64)RingInfo->RingBuffer->WriteIndex << 32)
- || RingInfo->RingBuffer->ReadIndex;
+ return (u64)RingInfo->RingBuffer->WriteIndex << 32;
}


--
1.6.0.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/