Hi Ted, > The my question is why if can not acquire the lock, abort the program? Is > there any special consideration? In general, the acquiring lock should succeed and it should wait if not acquired but it should not fail(will cause shared resource access violation).
Please do share (1.) the syslog just before 'Jun 10 06:49' and (2.) if there has been any specific 'test case'/platform as we don't see them on our setup. Thanks -Nagu > -----Original Message----- > From: Yao Cheng LIANG [mailto:[email protected]] > Sent: 11 June 2015 17:30 > To: [email protected] > Subject: [users] why osaf_mutex_lock_ordie > > Dear all, > > There are quite a few segmentation in my opensaf deployment, please see > below: > ---------------------------------------------------------------------------------------------------- > -rw------- 1 root root 2023424 Jun 10 06:49 1433890193-osafamfd-5394- > 18446744073709551615.core > -rw------- 1 root root 1761280 Jun 10 06:49 1433890193-osafamfnd-5405- > 18446744073709551615.core > -rw------- 1 root root 1179648 Jun 10 06:49 1433890193-osafamfwd-5503- > 18446744073709551615.core > -rw------- 1 root root 1236992 Jun 10 06:49 1433890193-osafckptd-5539- > 18446744073709551615.core > -rw------- 1 root root 2183168 Jun 10 06:49 1433890193-osafckptnd-6388- > 18446744073709551615.core > -rw------- 1 root root 1363968 Jun 10 06:49 1433890193-osafclmd-5373- > 18446744073709551615.core > -rw------- 1 root root 1179648 Jun 10 06:49 1433890193-osafclmna-5384- > 18446744073709551615.core > -rw------- 1 root root 1212416 Jun 10 06:49 1433890193-osafevtd-5529- > 18446744073709551615.core > -rw------- 1 root root 1318912 Jun 10 06:49 1433890193-osaffmd-5315- > 18446744073709551615.core > -rw------- 1 root root 9793536 Jun 10 06:49 1433890193-osafimmd-5326- > 18446744073709551615.core > -rw------- 1 root root 19095552 Jun 10 06:49 1433890193-osafimmnd-5337- > 18446744073709551615.core > -rw------- 1 root root 1212416 Jun 10 06:49 1433890193-osaflckd-5509- > 18446744073709551615.core > -rw------- 1 root root 1191936 Jun 10 06:49 1433890193-osaflcknd-5470- > 18446744073709551615.core > -rw------- 1 root root 9752576 Jun 10 06:49 1433890193-osaflogd-5348- > 18446744073709551615.core > -rw------- 1 root root 1228800 Jun 10 06:49 1433890193-osafmsgd-5459- > 18446744073709551615.core > -rw------- 1 root root 9621504 Jun 10 06:49 1433890193-osafmsgnd-5439- > 18446744073709551615.core > -rw------- 1 root root 1495040 Jun 10 06:49 1433890193-osafntfd-5362- > 18446744073709551615.core > -rw------- 1 root root 1179648 Jun 10 06:49 1433890193-osafrded-5305- > 18446744073709551615.core > -rw------- 1 root root 1490944 Jun 10 06:49 1433890193-osafsmfd-5427- > 18446744073709551615.core > -rw------- 1 root root 1187840 Jun 10 06:49 1433890193-osafsmfnd-5421- > 18446744073709551615.core > --------------------------------------------------- > > I found most of them are generated by osaf_mutex_lock_ordie, and the > definition is as below: > ----------------------------------------------------- > static inline void osaf_mutex_lock_ordie(pthread_mutex_t* io_mutex) > { > int result = pthread_mutex_lock(io_mutex); > if (result != 0) osaf_abort(result); > } > ------------------------------------------------ > The my question is why if can not acquire the lock, abort the program? Is > there any special consideration? > > Thanks. > > Ted > > Sent from Windows Mail > > ------------------------------------------------------------------------------ > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
