Summary: log: fix trouble when the number app streams reachs limitation [#1446]
Review request for Trac Ticket(s): #1446
Peer Reviewer(s): Lennart, Anders W, Mathi, Vu
Pull request to: Lenart
Affected branch(es): 4.6, 4.7, default
Development branch: default
--------------------------------
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>>
changeset 7214b787efa1088e407c89b016d0d16f30254c1a
Author: Canh Truong <canh.v.tru...@dektech.com.au>
Date: Wed, 16 Mar 2016 10:31:24 +0700
log: fix trouble when the number app streams reachs limitation [#1446]
If number of app stream has reached the limitation, logsv get failed to
add
this stream to stream array in ccbApplyCallback even though immsv
creates
object successfully. This patch help check the limitation of app stream
and
return the error to abort creating new app stream and new object.
Complete diffstat:
------------------
osaf/services/saf/logsv/lgs/lgs_evt.cc | 6 ++++++
osaf/services/saf/logsv/lgs/lgs_imm.cc | 7 ++++++-
osaf/services/saf/logsv/lgs/lgs_stream.cc | 12 ++++++++++++
osaf/services/saf/logsv/lgs/lgs_stream.h | 1 +
tests/logsv/tet_LogOiOps.c | 74
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/logsv/tet_saLogStreamOpen_2.c | 72
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 171 insertions(+), 1 deletions(-)
Testing Commands:
-----------------
There are two new test cases to test solution of issue.
Run following commands to test:
logtest 2 52
logtest 5 28
Testing, Expected Results:
--------------------------
All test cases passed
Conditions of Submission:
-------------------------
Get ack from peer 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 ~/.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.
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
