Summary: lck: fix errors when displaying SaLckResource class [#2070]
Review request for Ticket(s): 2070
Peer Reviewer(s): Ravi
Pull request to:
Affected branch(es): develop
Development branch: ticket-2070
Base revision: 1ca82324e733acd3a2fc9272253a65df7ed31baa
Personal repository: git://git.code.sf.net/u/trguitar/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):
---------------------------------------------
This patch fixes the bugs and adds tests to check them.
revision 8fe4377c25259e1430717d3b67e2c4cc2fd3c66f
Author: Alex Jones <ajo...@rbbn.com>
Date: Mon, 7 May 2018 10:04:42 -0400
lck: fix errors when displaying SaLckResource class [#2070]
When getting IMM info for a lock resource, SaLckResource, the information is
often not correct.
Both lckd and lcknd are not updating IMM correctly when SaLckResource
information changes at runtime.
Write test cases which make sure these attributes are being updated correctly.
And fix the issues.
Complete diffstat:
------------------
src/lck/Makefile.am | 5 ++-
src/lck/apitest/test_saLckLimitGet.cc | 4 ++
src/lck/lckd/gld_evt.c | 17 +++++---
src/lck/lckd/gld_rsc.c | 26 ++++++------
src/lck/lckd/gld_standby.c | 2 +-
src/lck/lcknd/glnd_client.c | 76 +++++++++++++++++------------------
src/lck/lcknd/glnd_client.h | 4 --
src/lck/lcknd/glnd_evt.c | 48 ++++++++++++++--------
src/lck/lcknd/glnd_res.c | 24 +++++++----
9 files changed, 121 insertions(+), 85 deletions(-)
Testing Commands:
-----------------
1) run the lcktest executable
Testing, Expected Results:
--------------------------
1) all tests should pass
Conditions of Submission:
-------------------------
May 13, or ack from developer
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 ~/.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
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
