[Pacemaker] crmd Segmentation fault at pacemaker 1.0.12

[TAKATSUKA Haruka]

Hello Andrew,
Thank you for the quick modification.

(Unfortunately the confirmation test is not possible because I don't understand
 a reproduction method for this crash ...)

regards,
---
Haruka Takatsuka


On Thu, 14 Nov 2013 09:32:24 +1100
Andrew Beekhof <andrew at beekhof.net> wrote:

> 
> On 13 Nov 2013, at 7:36 pm, TAKATSUKA Haruka <harukat at sraoss.co.jp> wrote:
> 
> > Hello,  pacemaker hackers
> > 
> > I report crmd's crash at pacemaker 1.0.12 .
> > 
> > We are going to upgrade pacemaker 1.0.12 to 1.0.13 .
> > But I was not able to find a fix for this problem from ChangeLog.
> > tengine.c:do_te_invoke() is not seem to care for transition_graph==NULL
> > case in even 1.0.x head code.
> 
> This should help:
> 
> https://github.com/ClusterLabs/pacemaker-1.0/commit/20f169d9cccb6c889946c64ab09ab4fb7f572f7c
> 
> > 
> > regards,
> > Haruka Takatsuka.
> > -----
> > 
> > [log]
> > Nov 07 00:00:08 srv1 crmd: [21843]: ERROR: crm_abort: abort_transition_graph: Triggered assert at te_utils.c:259 : transition_graph != NULL
> > Nov 07 00:00:08 srv1 heartbeat: [21823]: WARN: Managed /usr/lib64/heartbeat/crmd process 21843 killed by signal 11 [SIGSEGV - Segmentation violation].
> > Nov 07 00:00:08 srv1 heartbeat: [21823]: ERROR: Managed /usr/lib64/heartbeat/crmd process 21843 dumped core
> > Nov 07 00:00:08 srv1 heartbeat: [21823]: EMERG: Rebooting system.  Reason: /usr/lib64/heartbeat/crmd
> > 
> > [gdb]
> > $ gdb -c core.21843 -s crmd.debug crmd
> > --(snip)--
> > Program terminated with signal 11, Segmentation fault.
> > #0  0x00000000004199c4 in do_te_invoke (action=140737488355328,
> >    cause=C_FSA_INTERNAL, cur_state=S_POLICY_ENGINE,
> >    current_input=I_FINALIZED, msg_data=0x1b28e20) at tengine.c:186
> > 186                     if(transition_graph->complete == FALSE) {
> > --(snip)--