On 05/07/2011 01:27 PM, Pedro Scarapicchia Junior wrote:
Hi Stefan,
Thanks for the comment.
I believe that it is possible to release the memory at v9fs_walk.
However v9fs_walk_complete() is called from two another
functions: v9fs_walk_post_newfid_lstat()
and v9fs_walk_post_oldfid_lstat().
On Fri, May 6, 2011 at 8:05 PM, Pedro Scarapicchia Junior
pedrinho.re...@gmail.com wrote:
At v9fs_walk_complete(), the memory allocated at v9fs_walk() is not being
released leading system to crash due out of memory.
This patch releases structure V9fsWalkState after v9fs_walk is complete.
Am 07.05.2011 10:34, schrieb Stefan Hajnoczi:
On Fri, May 6, 2011 at 8:05 PM, Pedro Scarapicchia Junior
pedrinho.re...@gmail.com wrote:
At v9fs_walk_complete(), the memory allocated at v9fs_walk() is not being
released leading system to crash due out of memory.
This patch releases structure
Hi Stefan,
Thanks for the comment.
I believe that it is possible to release the memory at v9fs_walk. However
v9fs_walk_complete() is called from two another
functions: v9fs_walk_post_newfid_lstat() and v9fs_walk_post_oldfid_lstat().
Placing qemu_free at end of v9fs_walk_complete() solve memory
At v9fs_walk_complete(), the memory allocated at v9fs_walk() is not being
released leading system to crash due out of memory.
This patch releases structure V9fsWalkState after v9fs_walk is complete.
Signed-off-by: Pedro Scarapicchia Junior pedro.scarapic...@br.flextronics.com
---
