Version: 1
-Previous: f01c4073c3d8e8c4486a9fe0e4b4f1525f481e49
-Head: 0a02ac93d7287bbdc48578efcf676190572718f1
+Previous: 44e3e873c534254f059d0eba96b2e5df884ba733
+Head: c8a3f3a71764175b650ebc214143acef3cee6dcb
Applied:
+ srq: c8a3f3a71764175b650ebc214143acef3cee6dcb
Unapplied:
wv-rm-ioctl: f1e558769c5840f4359d9026feae0725a00510e3
wv-ver: 3fdcf3b5cc9e4a718b02ade74d0e8d0fb8498598
--- /dev/null
+Bottom: 06cdce656914daffeb60188020c0cbccef3f6806
+Top: 06cdce656914daffeb60188020c0cbccef3f6806
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2010-07-15 10:49:16 -0700
+
+winverbs: fix memory violation in SRQ code
+
+Problem reported by Shiqing Fan:
+
+"I got a memory violation error in wv_srq.cpp Query() function around
+line 202. It seems using uninitialized verbsData.output_size for
+memcpy. The verbsData.input_size is initialized in WvPreQueryQp
+(wvuverbs.cpp), and it has a similar memcpy in this function too."
+
+wv_uverbs.cpp should initialize the output_size to 0 in all
+WvPre* calls.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+