Hi AndersBj,
Reviewed the patch.
Ack.
/Neel.
On Tuesday 16 September 2014 01:16 PM, Anders Bjornerstedt wrote:
> osaf/services/saf/immsv/immnd/immnd_evt.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
> diff --git a/osaf/services/saf/immsv/immnd/immnd_evt.c
> b/osaf/services/saf/immsv/immnd/immnd_evt.c
> --- a/osaf/services/saf/immsv/immnd/immnd_evt.c
> +++ b/osaf/services/saf/immsv/immnd/immnd_evt.c
> @@ -2877,11 +2877,11 @@ static uint32_t immnd_evt_proc_fevs_forw
>
> immModel_setAdmReqContinuation(cb, saInv, conn);
>
> - } else if((evt->info.fevsReq.sender_count == 0x1) &&
> !(cl_node->mIsSync) &&
> + } else if((evt->info.fevsReq.sender_count == 0x1) && !(cl_node
> && cl_node->mIsSync) &&
> (immModel_immNotWritable(cb) || (cb->mSyncFinalizing
> && cb->fevs_out_count))) {
> /* sender_count set to 1 if we are to check locally for
> writability
> before sending to IMMD. This to avoid broadcasting
> requests that
> - are doomed anyway. The clause '!(cl_node->mIsSync)'
> is there to
> + are doomed anyway. The clause '!(cl_node &&
> cl_node->mIsSync)' is there to
> allow the immsync process to use saImmOmClassCreate.
> The local
> check is skipped for immsync resulting in the
> class-creaet message
> to be broadcast over fevs. The class create will be
> rejected at
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel