- **status**: review --> fixed
- **Comment**:
default (5.1) [staging:56c069]
changeset: 7634:56c06993b4c3
user: Hung Nguyen <[email protected]>
date: Fri May 13 12:57:29 2016 +0700
summary: imm: Assert isPbe and isApplier when receiving upcall [#1814]
opensaf-5.0.x [staging:de79cf]
changeset: 7635:de79cf144234
branch: opensaf-5.0.x
user: Hung Nguyen <[email protected]>
date: Fri May 13 12:57:29 2016 +0700
summary: imm: Assert isPbe and isApplier when receiving upcall [#1814]
opensaf-4.7.x [staging:26e591]
changeset: 7636:26e591ab94ce
branch: opensaf-4.7.x
user: Hung Nguyen <[email protected]>
date: Fri May 13 12:57:29 2016 +0700
summary: imm: Assert isPbe and isApplier when receiving upcall [#1814]
---
** [tickets:#1814] imm: Applier crashes when dispatching after clearing
implementer**
**Status:** fixed
**Milestone:** 4.7.2
**Created:** Mon May 09, 2016 03:50 AM UTC by Hung Nguyen
**Last Updated:** Thu May 12, 2016 04:20 AM UTC
**Owner:** Hung Nguyen
**Attachments:**
- [logs.7z](https://sourceforge.net/p/opensaf/tickets/1814/attachment/logs.7z)
(24.6 MB; application/octet-stream)
When the node is shutting down, the applications release their implementer
names (in SaAmfCSISetCallbackT).
If there's a ccb operation at that time, there's a chance that the applier will
Dispatch() after OiImplementerClear().
May 2 19:28:07 SC-2-2 opensafd: Stopping OpenSAF Services
May 2 19:28:07 SC-2-2 osafamfnd[4920]: NO Shutdown initiated
May 2 19:28:07 SC-2-2 osafimmnd[4850]: NO ERR_BUSY: ccb 272 is active on
object CmwMonitorIspId=1,CmwMonitorId=1,CmwSysConfigId=1 of class
CmwMonitorIsp. Can not release class applier
May 2 19:28:07 SC-2-2 clustermonitor: immutil_saImmOiClassImplementerRelease
CmwMonitorIsp failed, rc = 10
May 2 19:28:07 SC-2-2 osafimmnd[4850]: NO Implementer disconnected 60 <667,
2020f> (@ClusMonEE)
May 2 19:28:07 SC-2-2 clustermonitor: EE_Oi_Imp::releaseApplier CmwMonitorIsp
May 2 19:28:07 SC-2-2 clustermonitor:
../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2939:
imma_process_callback_info: Assertion 'cl_node->isPbe || cl_node->isApplier'
failed.
'cl_node->isApplier' is set to false in OiImplementerClear(), that's why it
fails to assert when dispatching.
Log and traces are attached to this ticket.
---
Test app is attached to this ticket.
root@SC-1:~# immcfg -f test_class.xml
root@SC-1:~# ./oi_applier &
root@SC-1:~# immcfg -c Test test=1
[1]+ Aborted (core dumped) ./oi_applier
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
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-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
