snep: fix fragmented response memory leaks
Sending long response might cause frame fragmentation and
near_snep_core_response_with_info() does not free such 'struct
p2p_snep_put_req_data'. It looks like freeing the fragmented response
is task for snep_core_process_request as it already frees the fragments.
Add also freeing the response itself to fix Valgrind (and ASAN) reported
memory leaks:
$ valgrind --leak-check=full unit/test-snep-read
80 bytes in 2 blocks are definitely lost in loss record 55 of 60
at 0x483ED99: calloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x122496: near_snep_core_response_with_info (snep.c:762)
by 0x122E21: test_snep_dummy_req_get (test-snep-read.c:179)
by 0x121FF3: snep_core_process_request (snep.c:411)
by 0x121FF3: near_snep_core_read (snep.c:616)
by 0x122CC4: test_snep_read_req_common (test-snep-read.c:355)
by 0x124792: test_snep_read_get_req_frags_client_resp (test-snep-read.c:760)
by 0x48ECDCD: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.1)
by 0x48ECBCA: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.1)
by 0x48ED2B9: g_test_run_suite (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.1)
by 0x48ED2D4: g_test_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.1)
by 0x10F982: main (test-snep-read.c:976)
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
1 file changed
