From: Zoran M. <zor...@er...> - 2017-01-10 16:28:24
|
Summary: ckpt: fix memory leak in saCkptCheckpointRead [#2256] Review request for Trac Ticket(s): 2256 Peer Reviewer(s): Mahesh, Vu Pull request to: Zoran Affected branch(es): opensaf-5.0.x, opensaf-5.1.x, default(5.2) Development branch: default(5.2) -------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services y OpenSAF services n Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- changeset eea7b196b146baa5fdf4e854a2f5ceab805daf95 Author: Zoran Milinkovic <zor...@er...> Date: Tue, 10 Jan 2017 17:24:59 +0100 ckpt: fix memory leak in saCkptCheckpointRead [#2256] Allocated memory in cpa_proc_build_data_access_evt() is freed. Complete diffstat: ------------------ src/ckpt/agent/cpa_proc.c | 22 ++++++++++++++++------ 1 files changed, 16 insertions(+), 6 deletions(-) Testing Commands: ----------------- Testing, Expected Results: -------------------------- Run ckpttest with valgrind and check that the reported memory leaks are gone Conditions of Submission: ------------------------- Ack from Mahesh and Vu Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 n n powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.hgrc file (i.e. username, email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. |