Page MenuHomeClusterLabs Projects

Don't allow id-ref to parent rule within nested rule
Open, NormalPublic

Assigned To
None
Authored By
nrwahl2
Thu, Jul 4, 2:28 PM
Tags
  • Restricted Project
  • Restricted Project
  • Restricted Project
Referenced Files
None
Subscribers

Description

The following results in an infinite loop within Pacemaker:

<rule id="rule1">
  <rule id-ref="rule1"/>
</rule>

I don't know if a RelaxNG schema can prevent this, but Pacemaker should at least throw an error. Currently it segfaults on my machine.

Since rules can be arbitrarily nested, we should throw an error if a rule's id-ref resolves to any ancestor, not just the immediate parent.

Event Timeline

nrwahl2 triaged this task as Normal priority.Thu, Jul 4, 2:28 PM
nrwahl2 created this task.
nrwahl2 created this object with edit policy "Restricted Project (Project)".
nrwahl2 added a project: Restricted Project.
nrwahl2 updated the task description. (Show Details)