dpa_offload: Avoid illegal access of IPSec instance after release

The function "dpa_ipsec_free" is calling "free_resources" which
is releasing the dpa_ipsec instance by executing

kfree(dpa_ipsec);

Once this call ends, "dpa_ipsec_free" is accessing again the
"instance" pointer to call "mark_unused_gbl_dpa_ipsec". The problem
is that the "instance" pointer is inconsistent at his point (was
released by the call to "free_resources").

To fix this, the call to "mark_unused_gbl_dpa_ipsec" was simply
removed from "dpa_ipsec_free" because the function "free_resources"
is already doing that.

Signed-off-by: Marian Chereji <marian.chereji@freescale.com>
Change-Id: Ibabc69253a8a21c7bb158bc371193a6b9ace01ac
Reviewed-on: http://git.am.freescale.net:8181/36404
Tested-by: Review Code-CDREVIEW <CDREVIEW@freescale.com>
Reviewed-by: Pinghua An <pinghua.an@freescale.com>
Reviewed-by: Honghua Yin <Hong-Hua.Yin@freescale.com>

0 files changed, 0 insertions, 0 deletions