Summary: <<FILL ME>>
Review request for Trac Ticket(s): 778
Peer Reviewer(s): Praveen
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): all
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 f934d942141e142faaa4ef66ba5f17947de70531
Author: Hans Feldt <hans.fe...@ericsson.com>
Date: Tue, 11 Feb 2014 14:33:03 +0100
amfnd: handle avadown in shutting down [#778]
If a component crash/exits during opensaf shutdown it will delay the
shutdown with the component configured callback timeout.
The reason is that the avadown event is ignored in the shutdown state.
This
results in amfnd sends a terminate callback request to an already
terminated
process.
This is fixed by handling the avadown event and launch the cleanup
script
for the component. This changes the presence state to terminating thus
the
send of the terminate request will be skipped.
Complete diffstat:
------------------
osaf/services/saf/amf/amfnd/comp.cc | 8 +-------
1 files changed, 1 insertions(+), 7 deletions(-)
Testing Commands:
-----------------
* Load a model with (at least) one SU, with three components. One SI with three
CSIs each assigned to its own component. CSI deps.
* unlock the SU
* shutdown opensaf
* comp1 gets the first CSI remove callback, do not respond
* crash comp2
Testing, Expected Results:
--------------------------
Without patch CSI remove is sent and shutdown delayed with the callback
timeout. With patch no delay in shutdown.
Conditions of Submission:
-------------------------
Ack from Praveen
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.
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
