Activity for Hoa Le
-
Hoa Le committed [a67972]
mdstest: identify svcs using svc_id and mds_dest when storing event info [#2798]
-
mdstest: correct timing issues in mdstest [#2798]
-
mdstest: identify svcs using svc_id and mds_dest when storing event info [#2798]
-
mdstest: correct timing issues in mdstest [#2798]
-
ntf: coredump if ntfimcnd misses the fake modify callback
-
commit 0f5a0a6d83aab679050d5057b496fd4e2e42ec8a (HEAD, origin/develop, develop) Author: Hoa Le hoa.le@dektech.com.au Date: Mon Jun 4 10:53:19 2018 +0700 ntf: restart ntfimcnd if operation invoker name is missing [#2859] If ntfimcnd was restarted during a CCB, it might receive ObjectDelete operation as the first event. ccbUtilCcbData, which was initialized in this case, does not contain the operation invoker name. This causes ntfimcnd to crash and generates a coredump when the ccbUtilCcbData being...
-
ntf: coredump if ntfimcnd misses the fake modify callback
-
https://sourceforge.net/p/opensaf/mailman/message/36333847/
-
ntf: restart ntfimcnd if operation invoker name is missing [#2859]
-
ntf: Wrong AdminOwnerName notified by osafntfimcnd
-
ntf: ntfimcnd exits when creating an object with empty SaNameT attribute
-
commit 64fa3420bad8ee5c2457f834f2430ecb958f6e34 (HEAD, origin/develop, develop) Author: Hoa Le hoa.le@dektech.com.au Date: Sat May 19 14:04:57 2018 +0700 ntf: fix ntfimcnd issue with empty SaNameT [#2854] ntfimcnd unexpectedly exits when reserving memory for empty SaNameT attribute. The issue happens becasue ntfimcnd passes the SaNameT's length which is 0, to saNtfPtrValAllocate function. This patch helps avoid the issue by increasing the SaNameT' length to 1 before passing it to the saNtfPtrValAllocate...
-
Thread 1 (Thread 0x7f3d30c16740 (LWP 496)): #0 osaf_extended_name_borrow (name=name@entry=0x0) at src/base/osaf_extended_name.c:95 length = <error reading variable length (Cannot access memory at address 0x0)> value = <optimized out> #1 0x000055d3410d2fe1 in ntfimcn_send_object_delete_notification (CcbUtilOperationData=CcbUtilOperationData@entry=0x55d342a71e30, invoke_name=0x0, ccbLast=ccbLast@entry=SA_FALSE) at src/ntf/ntfimcnd/ntfimcn_notifier.c:1501
-
ntf: coredump if ntfimcnd misses the fake modify callback
-
ntf: ntfimcnd exits when creating an object with empty SaNameT attribute
-
https://sourceforge.net/p/opensaf/mailman/message/36321036/
-
ntf: fix ntfimcnd issue with empty SaNameT [#2854]
-
ntf: ntfimcnd exits while notifying about 255 chars DN object
-
commit 26dae3c147f1e029ae15218d80e6c3f7191adfe8 Author: Hoa Le hoa.le@dektech.com.au Date: Mon May 14 10:19:32 2018 +0700 ntf: Don't use old style SaNameT with 255 chars DN in ntfimcnd [#2850] osafntfimcnd uses old style SaNameT when sending notification. The SaNameT's length will be adjusted to 256 when its value contains 255 characters excluded the NULL character. This SaNameT is now not a valid extended name and causes osafntfimcnd to exit. This patch helps avoid the above issue by using the new...
-
ntf: ntfimcnd exits when creating an object with empty SaNameT attribute
-
ntf: ntfimcnd exits while notifying about 255 chars DN object
-
https://sourceforge.net/p/opensaf/mailman/message/36316933/
-
ntf: Don't use old style SaNameT with 255 chars DN in ntfimcnd [#2850]
-
ntf: ntfimcnd exits while notifying about 255 chars DN object
-
mds: mdstest 14 1 perpetually hanging
-
Release branch: commit ddc727f9184508ff03929dd6c3f7971c8215959c Author: Hoa Le hoa.le@dektech.com.au Date: Mon Apr 9 18:35:15 2018 +0700 mds: Update test suite 14 to avoid perpetually hanging [#2831] Currently in suite 14, mdstest sends messages with MDS_SENDTYPE_SNDACK and MDS_SENDTYPE_SNDRSP types to the same destination, this sometimes makes the Response thread to catch the wrong event and does not respond to MDS_SENDTYPE_SNDRSP call. This causes the test case to hang forever. This patch changes...
-
imma: unexpected assertion if saImmOiAugmentCcbInitialize finalizes the privateOmHandle which was initialized from previous session
-
Release branch: commit 2f465f629915ce3ceffabdb05ce0022e1b031e02 Author: Hoa Le hoa.le@dektech.com.au Date: Tue Apr 3 09:34:34 2018 +0700 imma: Do not finalize previously instialized privateOmHandle in saImmOiAugmentCcbInitialize [#2827] Currently in saImmOiAugmentCcbInitialize, if OI augmented ccb handle initialization request does not result in OK or TRY_AGAIN, the privateOmHandle will be finalized and the private OM will be destroyed. That is fine if the privateOmHandle is initialized in the current...
-
mds: mdstest 14 1 perpetually hanging
-
https://sourceforge.net/p/opensaf/mailman/message/36289056/
-
mds: Update test suite 14 to avoid perpetually hanging [#2831]
-
mds: mdstest 14 1 perpetually hanging
-
imma: unexpected assertion if saImmOiAugmentCcbInitialize finalizes the privateOmHandle which was initialized from previous session
-
imma: Do not finalize previously instialized privateOmHandle in saImmOiAugmentCcbInitialize [#2827]
-
mds: mdstest 14 1 perpetually hanging
-
imma: unexpected assertion if saImmOiAugmentCcbInitialize finalizes the privateOmHandle which was initialized from previous session
-
Release branch: commit d158f2aa831a55673214c4e7640d1fcaaf7ce7b3 Author: Hoa Le hoa.le@dektech.com.au Date: Thu Mar 22 19:31:39 2018 +0700 mds: improve thread safety in mdstest [#2746] - Correct helgrind issues in mds/apitest commit 24f02c09aaf15b264b9e37fd945329db4f00701a Author: Hoa Le hoa.le@dektech.com.au Date: Tue Mar 27 14:11:35 2018 +0700 mds: improve thread safety in mdstest - part 2 [#2746] - Remove thread-local declaration of svc_to_mds_info Develop branch: commit dac6b5bf582e581252f21d32b470f91d5629b867...
-
mds: improve thread safety in mdstest - part 2 [#2746]
-
mds: improve thread safety in mdstest - part 2 [#2746]
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
https://sourceforge.net/p/opensaf/mailman/message/36275208/
-
mds: Correct timing issues in mdstest [#2798]
-
mds: mds test is not thread safe
-
Release branch: commit d158f2aa831a55673214c4e7640d1fcaaf7ce7b3 Author: Hoa Le hoa.le@dektech.com.au Date: Thu Mar 22 19:31:39 2018 +0700 mds: improve thread safety in mdstest [#2746] - Correct helgrind issues in mds/apitest Develop branch: commit dac6b5bf582e581252f21d32b470f91d5629b867 Author: Hoa Le hoa.le@dektech.com.au Date: Thu Mar 22 19:31:39 2018 +0700 mds: improve thread safety in mdstest [#2746] - Correct helgrind issues in mds/apitest
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
I would like to reopen this ticket since the issue is not identical with that in ticket #2746.
-
mds: improve thread safety in mdstest [#2746]
-
mds: mds test is not thread safe
-
https://sourceforge.net/p/opensaf/mailman/message/36269820/
-
mds: improve thread safety in mdstest [#2746]
-
mds: mds test is not thread safe
-
Sure, can you send me the current patch of ticket #2746 so I can work on it ?
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
cpnd: Wrong duration is passed to cpnd_tmr_start in cpnd_proc_update_remote
-
Release branch: commit 1b6b7380b344957e3e0c303bf0e4f13607adc7fe Author: Hoa Le hoa.le@dektech.com.au Date: Thu Mar 1 09:49:34 2018 +0700 cpnd: Correct duration of cpnd_tmr_start in cpnd_proc_update_remote [#2787] In cpnd_proc_update_remote() function, cpnd_tmr_start is invoked with the timer duration parameter being adjusted by m_CPSV_CONVERT_SATIME_TEN_MILLI_SEC. This duration is 0 in most cases, which will lead to SA_AIS_ERR_TIMEOUT error of checkpoint write action if the checkpoint data is big...
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
I did not have the full view on that ticket. In this case, I will close this ticket as it's a part of #2746.
-
It is my understanding that the issue reported in ticket #2746 is about data-race between mdstest threads when they use the same global variable. It doesn't seem to be duplicate of the issue in this ticket. The issue in this ticket is that, sometimes mdstest may request operations before the expected MDS service event arriving (and being processed) at MDS thread (mdtm_process_recv_events_tcp). For example, the test case 14 5 is used to verify the behavior of MDS when sending a message to services...
-
It is my understanding that the issue reported in ticket #2746 is about data-race between mdstest threads when they use the same global variable. It doesn't seem to be duplicate of the issue in this ticket. The issue in this ticket is that, sometimes mdstest may request operations before the expected MDS service event arriving (and being processed) at MDS thread (mdtm_process_recv_events_tcp). For example, the test case 14 5 is used to verify the behavior of MDS when sending a message to services...
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
MDS traces and logs of 5 9, 14 5, 14 6
-
MDS traces and logs of 10 1, 10 2
-
MDS traces and log of 4 10, 4 12
-
mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6 failed
-
https://sourceforge.net/p/opensaf/mailman/message/36242059/
-
cpnd: Correct duration of cpnd_tmr_start in cpnd_proc_update_remote [#2787]
-
cpnd: Correct duration of cpnd_tmr_start in cpnd_proc_update_remote [#2787]
-
cpnd: Wrong duration is passed to cpnd_tmr_start in cpnd_proc_update_remote
-
https://sourceforge.net/p/opensaf/mailman/message/36235734/
-
cpnd: Correct duration of cpnd_tmr_start in cpnd_proc_update_remote [#2787]
-
ckptnd: Correct duration of cpnd_tmr_start in cpnd_proc_update_remote [#2787]
-
cpnd: Wrong duration is passed to cpnd_tmr_start in cpnd_proc_update_remote
-
cpnd: Wrong duration is passed to cpnd_tmr_start in cpnd_proc_update_remote
-
pyosaf: High level python interfaces for LOG [#2602]
-
pyosaf: High level python interfaces for LOG [#2602]
-
pyosaf: High level python interfaces for LOG [#2602]
-
amfd: Segfaults in su/node_ccb_completed_delete_hdlr
-
amfd: Segfaults in su/node_ccb_completed_delete_hdlr
-
amfnd: Fix illegal memory access in avnd_comptype_delete [#2424]
-
amfnd: Fix illegal memory access in avnd_comptype_delete [#2424]
-
amfnd: Fix illegal memory access in avnd_compty...
-
amfnd: illegal memory access in avnd_comptype_delete()
-
amfnd: Fix illegal memory access in avnd_compty...
-
amfnd: illegal memory access in avnd_comptype_delete()
-
AMF: creating an SaAmfSIRankedSU object with rank==0 causes inconsistence
-
amfd: Correct coverity detected errors [#680]
-
AMF: Coverity issues in amfd/amfnd
-
amfd: Correct coverity detected errors [#680]
-
AMF: Coverity issues in amfd/amfnd
1