Summary: log: fix log supported maximum 2047 characters for long DN [#2525] Review request for Ticket(s): 2525 Peer Reviewer(s): Lennart, Vu, Mahesh Pull request to: Vu Affected branch(es): develop, release Development branch: ticket-2525 Base revision: 3be8e9adb4670607a93907a886b0cf301570d65a Personal repository: git://git.code.sf.net/u/canht32/review
-------------------------------- 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): --------------------------------------------- *** EXPLAIN/COMMENT THE PATCH SERIES HERE *** revision 81ba7f3323ab58677b706ca60075cf5b031cc4db Author: Canh Van Truong <[email protected]> Date: Wed, 12 Jul 2017 14:56:34 +0700 log: fix log supported maximum 2047 characters for long DN [#2525] Currently, log support maximum 2047 characters for long DN. it should support maximum 2048 characters. The patch also fixes to check SA_AMF_COMPONENT_NAME maximum 2048 characters and refactor encode and decode for SaNameT to process its name in one place Complete diffstat: ------------------ src/log/agent/lga_agent.cc | 4 +- src/log/agent/lga_mds.cc | 99 ++++++++++++++-------------- src/log/agent/lga_util.cc | 5 +- src/log/apitest/tet_log_longDN.c | 131 +++++++++++++++++++++++++++---------- src/log/logd/lgs_mds.cc | 137 +++++++++++++++------------------------ src/log/logd/lgs_recov.cc | 6 +- src/log/logd/lgs_util.cc | 5 +- 7 files changed, 210 insertions(+), 177 deletions(-) Testing Commands: ----------------- Update test cases: logtest 13 6, logtest 13 7, logtest 13 8 and create test case: logtest 13 11 Testing, Expected Results: -------------------------- All test cases pass Conditions of Submission: ------------------------- Ack from reviewers 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 ~/.gitconfig file (i.e. user.name, user.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. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
