Currently winmad does not support byte offset reads and writes. However, if we ever want to support that feature, than we need to specify an offset of 0 for current operations to avoid backwards compatibility issues.
Signed-off-by: Sean Hefty <sean.hefty@intel.com>
git-svn-id: svn://openib.tc.cornell.edu/gen1@2893
ad392aa1-c5ef-ae45-8dd8-
e69d62a5ef86
{\r
InitializeCriticalSection(&m_CritSecRead);\r
InitializeCriticalSection(&m_CritSecWrite);\r
- m_OverlapRead.hEvent = NULL;\r
- m_OverlapWrite.hEvent = NULL;\r
+ RtlZeroMemory(&m_OverlapRead, sizeof m_OverlapRead);\r
+ RtlZeroMemory(&m_OverlapWrite, sizeof m_OverlapWrite);\r
m_nRef = 1;\r
m_hFile = INVALID_HANDLE_VALUE;\r
InterlockedIncrement(&WmRef);\r