Public bug reported:
Binary package hint: openais
Description of problem:
exec/totem.h defines INTERFACE_MAX to 2. This is very limiting and it is not
coherent with the rest of the cluster stack.
openais limits to 2
kernel dlm to 3
dlm_controld to 4
Those values should be at least alligned to 4 or higher.
In theory a dynamic allocation here would be the winner.
with the default set to 2, configuring 3 rings in openais.conf (passive mode,
since active it totally broken), will lead openais to crash because of memory
corruption (there is no protection within the code to try to init and config
only INTERFACE_MAX).
Version-Release number of selected component (if applicable):
trunk
How reproducible:
always
Steps to Reproduce:
1. given default svn checkout
2. configure INTERFACE_MAX + 1 rings in passive mode
3. fire up aisexec.
(tested on amd64 with glibc-2.7 will report memory corruption detected
by glibc)
Actual results:
aisexec crashes and dies.
Expected results:
should work no matter how many rings i configure. hardcoded limitations are bad
and it is not even documented.
Additional info:
** Affects: openais (Ubuntu)
Importance: Undecided
Assignee: Soren Hansen (shawarma)
Status: New
** Affects: openais (Fedora)
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #424681
https://bugzilla.redhat.com/show_bug.cgi?id=424681
** Also affects: openais (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=424681
Importance: Unknown
Status: Unknown
** Changed in: openais (Ubuntu)
Assignee: (unassigned) => Soren Hansen (shawarma)
--
INTERFACE_MAX is not proper
https://bugs.launchpad.net/bugs/176299
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
