Ack, Tested on both tipc/tcp as transport. Note: Log test needs some timing related tuning on TCP transport though.
Thanks, Mathi. > -----Original Message----- > From: Lennart Lund [mailto:[email protected]] > Sent: Thursday, May 12, 2016 12:37 PM > To: Mathivanan Naickan Palanivelu > Cc: [email protected]; Vu Minh Nguyen; Lennart Lund > Subject: RE: [devel] [PATCH 0 of 1] Review Request for log: Deadlock in log > agent makes client hang [#1805] > > Hi Mathi > > Can you please review this one. > > Thanks > Lennart > > > -----Original Message----- > > From: Lennart Lund [mailto:[email protected]] > > Sent: den 9 maj 2016 12:44 > > To: [email protected]; Vu Minh Nguyen > > Cc: [email protected] > > Subject: [devel] [PATCH 0 of 1] Review Request for log: Deadlock in > > log agent makes client hang [#1805] > > > > Summary: log: Deadlock in log agent makes client hang Review request > > for Trac Ticket(s): #1805 Peer Reviewer(s): [email protected], > > Vu Minh Nguyen <[email protected]> Pull request to: <<LIST > > THE PERSON WITH PUSH ACCESS HERE>> Affected branch(es): 5.0, default > > Development branch: <<IF ANY GIVE THE REPO URL>> > > > > -------------------------------- > > 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): > > --------------------------------------------- > > See also previous review request > > > > changeset 94062eb3f7a314ee227d50a08d67466c0819971f > > Author: Lennart Lund <[email protected]> > > Date: Mon, 09 May 2016 12:35:47 +0200 > > > > log: Deadlock in log agent makes client hang [#1805] > > > > Remove deadlock when two mutexes conflict in MDS and log agent. > Make > > sure > > that cb_lock is not taken when calling any MDS API Some cleaning of > > code > > e.g. removing "dead" code and moving functions from lga_state.c > that > > are not > > related to lga_state.c > > > > > > Complete diffstat: > > ------------------ > > osaf/libs/agents/saf/lga/lga_api.c | 12 ++++++++++++ > > osaf/libs/agents/saf/lga/lga_mds.c | 9 ++++++--- > > osaf/libs/agents/saf/lga/lga_state.c | 80 > > +++++++++++++++++++++++------ > > --------------------------------------------------- > > osaf/libs/agents/saf/lga/lga_state.h | 4 ---- > > osaf/libs/agents/saf/lga/lga_util.c | 29 > > ++++++++++++++++++++++++++++- > > 5 files changed, 69 insertions(+), 65 deletions(-) > > > > > > Testing Commands: > > ----------------- > > <<LIST THE COMMAND LINE TOOLS/STEPS TO TEST YOUR CHANGES>> > > > > > > Testing, Expected Results: > > -------------------------- > > <<PASTE COMMAND OUTPUTS / TEST RESULTS>> > > > > > > Conditions of Submission: > > ------------------------- > > <<HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC>> > > > > > > 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. > > > > > > ---------------------------------------------------------------------- > > -------- Find and fix application performance issues faster with > > Applications Manager Applications Manager provides deep performance > > insights into multiple tiers of your business applications. It > > resolves application problems quickly and reduces your MTTR. Get your > > free trial! > > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > _______________________________________________ > > Opensaf-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/opensaf-devel ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
