#947 AMF: Segmentation violation in *__ccb_apply_cb at CCBUTIL_DELETE

[Hans Nordebäck]

Segmentation violations are encountered in sutcomptype_ccb_apply_cb et al.

At:
case CCBUTIL_DELETE:
comp_type = comptype_db->find(Amf::to_string(&opdata->objectName));
if (NULL != comp_type->list_of_comp) {

if not found, comp_type is 0 which is not checked. opdata->userData is set
to comp_type, now 0. This results in segmentation violation later in
sutcomptype_ccb_apply_cb.

To correct this:
case CCBUTIL_DELETE:
sutcomptype = sutcomptype_db->find(Amf::to_string(&opdata->objectName));
if (sutcomptype == 0)
goto done;

why the object is not found should be investigated, are there problems with
std::string vs. SaNameT, i.e garbage etc. in SaNameT? /Hans

[Hans Nordebäck]

The patch sent out doesn't seem to work/solve the problem.

[Hans Nordebäck]

This may be caused by the #305 patch, "skip processing of ccb completed cbk at standby amfd [#305]"

[Praveen]

Published Review Request for:
"amfd : standby AMFD should process ccb completed cbk for delete [#947]"

[Praveen]

changeset: 5451:4bbd25649ce9
tag: tip
parent: 5448:388e290fc122
user: praveen.malviya@oracle.com
date: Mon Jun 30 16:19:46 2014 +0530
summary: amfd : standby AMFD should process ccb completed cbk for delete [#947]

changeset: 5450:e26b505501ad
branch: opensaf-4.4.x
parent: 5447:6b3fef573fe7
user: praveen.malviya@oracle.com
date: Mon Jun 30 16:19:03 2014 +0530
summary: amfd : standby AMFD should process ccb completed cbk for delete [#947]

changeset: 5449:fbd78722aaaf
branch: opensaf-4.3.x
parent: 5446:7ba3b6f573a1
user: praveen.malviya@oracle.com
date: Mon Jun 30 16:15:39 2014 +0530
summary: amfd : standby AMFD should process ccb completed cbk for delete [#947]

[staging:fbd787]
[staging:e26b50]
[staging:4bbd25]