- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,6 +1,8 @@
-Dec 5 18:25:24 SC-1 local0.notice osafimmnd[510]: NO Clear 1 search result(s)
for OM handle 140002010f. Search timeout 600sec
+The data types of these attributes `osafAmfDelayNodeFailoverTimeout` and
`osafAmfDelayNodeFailoverNodeWaitTimeout` are `time_t`, but the method
`Configuration::get_config()` uses an incorrect container, it is `uint32_t`, to
hold the values of those attributes and it leads to the stack memory corrupted.
Actually, it is the local variable `searchHandle` that is corrupted; since the
second searchnext interation, the value of this handle is changed to a wrong
number, so the searchhandle is leaked with below message in syslog:
-Step to reproduce :
-1. Run uml cluster
+> Dec 5 18:25:24 SC-1 local0.notice osafimmnd[510]: NO Clear 1 search
result(s) for OM handle 140002010f. Search timeout 600sec
+
+Steps to reproduce :
+1. Start uml cluster
2. Wait for sometime and you will see that msg in syslog
~~~~
---
** [tickets:#3128] AMFD: stack memory is corrupted inside
Configuration::get_config()**
**Status:** assigned
**Milestone:** 5.20.01
**Created:** Mon Dec 09, 2019 02:59 AM UTC by Chau Hoang Phuc
**Last Updated:** Mon Dec 09, 2019 02:59 AM UTC
**Owner:** Chau Hoang Phuc
The data types of these attributes `osafAmfDelayNodeFailoverTimeout` and
`osafAmfDelayNodeFailoverNodeWaitTimeout` are `time_t`, but the method
`Configuration::get_config()` uses an incorrect container, it is `uint32_t`, to
hold the values of those attributes and it leads to the stack memory corrupted.
Actually, it is the local variable `searchHandle` that is corrupted; since the
second searchnext interation, the value of this handle is changed to a wrong
number, so the searchhandle is leaked with below message in syslog:
> Dec 5 18:25:24 SC-1 local0.notice osafimmnd[510]: NO Clear 1 search
> result(s) for OM handle 140002010f. Search timeout 600sec
Steps to reproduce :
1. Start uml cluster
2. Wait for sometime and you will see that msg in syslog
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
