gk20a memory management code did not correctly drop reference to
nvmap handle or nvmap client if we were unable to actually map
the memory to gk20a memory space. This leaded to memory leaks in
some use cases.
Bug
1408131
Change-Id: If99de665ffeb984df2a41aa4edbaddf30e84af9f
Signed-off-by: Arto Merilainen <amerilainen@nvidia.com>
Reviewed-on: http://git-master/r/350630
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
flags, 0/*no kind here, to be removed*/, NULL, true,
mem_flag_none);
*offset_align = ret_va;
- if (!ret_va)
+ if (!ret_va) {
+ nvhost_memmgr_put(memmgr, r);
+ nvhost_memmgr_put_mgr(memmgr);
err = -EINVAL;
+ }
return err;
}