Summary: ntfs: init with CLM in a separate thread to avoid deadlock situation[#1731] Review request for Trac Ticket(s): #1731 Peer Reviewer(s): Lennart Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>> Affected branch(es): 5.0 and 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): --------------------------------------------- changeset f428787801eaf22163f8ea48446a9a63e9b2d03a Author: [email protected] Date: Wed, 06 Apr 2016 18:10:32 +0530 ntfs: init with CLM in a separate thread to avoid deadlock situation[#1731] Deadlock situation may arise when NTFS tries to initialize with CLM and at the same time CLM is trying to send some notification. The issue is seen in UML environment. Patch fixes the problem by initializing with CLM in a separate thread at NTFS. Complete diffstat: ------------------ osaf/services/saf/ntfsv/ntfs/ntfs.h | 2 +- osaf/services/saf/ntfsv/ntfs/ntfs_cb.h | 1 + osaf/services/saf/ntfsv/ntfs/ntfs_clm.c | 43 +++++++++++++++++++++++++++++++++---------- osaf/services/saf/ntfsv/ntfs/ntfs_com.c | 2 +- osaf/services/saf/ntfsv/ntfs/ntfs_evt.c | 2 ++ osaf/services/saf/ntfsv/ntfs/ntfs_main.c | 35 +++++++++++++++-------------------- osaf/services/saf/ntfsv/ntfs/ntfs_mds.c | 6 +++++- 7 files changed, 58 insertions(+), 33 deletions(-) Testing Commands: ----------------- Bring up opensaf 4 nodes in UML environment. Run ntftests Testing, Expected Results: -------------------------- Opensaf must come up successfully. All ntf test cases including the CLM integation test case must pass. Conditions of Submission: ------------------------- Ack from the reviewer. Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 y y 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. ------------------------------------------------------------------------------ _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
