Red Hat Bugzilla – Bug 506729
SAF Test lck: saLckResourceClose/3-2
Last modified: 2009-06-29 17:55:49 EDT
Created attachment 348470 [details]
Description of problem:
Version-Release number of selected component (if applicable):
Compile and run included files
Steps to Reproduce:
Again nice select, so
Call the api to test if the pending request is dropped,when the requestor
has a pending EX mode lock request against the lock resource.
1. open a resource to lock.
2. fork a child process , in the child process ,to lock the resource
using PR lock,and then send a signal SIGUSR1 to father process,and
3. father process lock the same resource using
EX lock, and then close the resource,and then test if the pending
request is dropped.
4. father process send a signal to child process,let it go on and
5. father wait for child process' terminal.
Return = SA_AIS_OK
3-fork.c is the child process.
For me, it looks like good test
Created attachment 348471 [details]
Child of main program
Created attachment 349882 [details]
New saLckResourceClose/3-2.c test case.
Here is a new version of saLckResourceClose/3-2.c that does not use select to
determine is a callback has been made.
Closing this as fixed upstream. OpenAIS lock service now has code to
cancel/skip callbacks for resources that have been closed with pending
callbacks. Fix for saftest code it attached above.