Menu
▾
▴
Re: [LTP] Re: fcntl14 & fcntl16 is failed while doing mandatory locking.
|
From: <vis...@sa...> - 2004-07-30 08:57:26
|
Hi,
For your information
log
-----
#./fcntl16
fcntl16 0 INFO : Entering block 1
fcntl16 0 INFO : Test case 1:without mandatory locking PASSED
fcntl16 0 INFO : Exit block 1
fcntl16 0 INFO : Entering block 2
fcntl16 1 FAIL : First parent lock failed
fcntl16 2 FAIL : Test case 1, errno = 37
fcntl16 0 INFO : Test case 2: With mandatory record locking FAILED
fcntl16 0 INFO : Exiting block 2
fcntl16 0 INFO : Entering block 3
fcntl16 3 FAIL : First parent lock failed
fcntl16 4 FAIL : Test case 1, errno = 37
fcntl16 0 INFO : Test case 2: With mandatory locking with NODELAY
FAILED
fcntl16 0 INFO : Exiting block 3
#
>> Thanks for the Reply Robert,
> I am able to successfully execute one simple program that do mandatory
> locking on the file(I think no problem with nolock option, morever lockd
> is running on nfs server).And also all fcntl testcases in LTP have
> passed exept fcntl14 & fcntl16 on ARM.
> I found that in fcntl16.c, we are not doing file unlock(F_UNLCK), just
> keep on applying mandatory locks in block2. So this would result in the
> number of locked regions in the system exceeding a system-imposed
> limit.Probably that's why i am getting the ENOLOCK error(it returns when
> remote NFS protocol fails).
>
> Is there any limits for madatory locks we can appply on a file?
> IF you any thoughts, let me know.
>
> Thankx
> Vishwa
>
>>
>>
>> Well if you mount with "nolock" as an option, I would expect to see
>> errors on any test that attempts to do file locking on that mounted
>> filesystem.
>>
>> -Robbie
>> (Embedded image moved to file: pic05448.jpg)
>>
>>
>>
>> <vishwahg@sasken.
>> com>
>> Sent by:
>> To ltp-list-admin@li
>> <ltp...@li...> sts.sourceforge.n
>> cc et
>> <pra...@ti...>,
>> <x00...@sa...>
>>
>> Subject
>>
>> 07/29/2004 07:03 [LTP] Re: fcntl14 & fcntl16 is
>> AM failed while doing mandatory
>>
>> locking.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi,
>>
>> The following system call tests have failed on ARM over NFS mounted
>> filesystem.
>>
>> 1.fcntl14.c & fcntl16.c-- These have failed while doing mandatory
>> locking For example in run_test function in fcntl16.c
>>
>> fd = open(tmpname, O_CREAT | O_RDWR | O_TRUNC,S_IRUSR |
>> S_IWUSR)
>>
>> /* then write 10 bytes to tmpname and apply mandatory
>> lock*/
>> /* write some dummy data to the file */
>> (void)write(fd, FILEDATA, 10);
>>
>> thislock->l_type = F_WRLCK;
>> thislock->l_whence = 0;
>> thislock->l_length = 0; /* until EOF */
>> thislock->flag= IGNORED
>> /* set the initial parent lock on the file */
>> if ((fcntl(fd, F_SETLK, thislock)) < 0) {
>> tst_resm(TFAIL, "First parent
>> lock
>> failed");
>> tst_resm(TFAIL, "Test case %d,
>> errno =
>> %d", test + 1,
>> errno);
>> unlink(tmpname);
>> return(1);
>> }
>>
>> I got the error : ENOLOCK -The argument cmd(thislock) is F_SETLK or
>> F_SETLKW and satisfying the lock or unlock request would result in the
>> number of locked regions in the system exceeding a system-imposed
>> limit. INFO:
>> I mounted the NFS with nolock option.
>>
>> Is it possible do mandatory locking on file which is nfs mounted? If
>> you have any thoughts? Let me know.
>>
>> Thankx
>> Vishwa
>>
>>
>>
>>
>>
>> SASKEN BUSINESS DISCLAIMER
>> This message may contain confidential, proprietary or legally
>> Privileged information. In case you are not the original intended
>> Recipient of the message, you must not, directly or indirectly, use,
>> Disclose,
>> distribute, print, or copy any part of this message and you are
>> requested to delete it and inform the sender. Any views expressed in
>> this message are those of the individual sender unless otherwise
>> stated. Nothing contained in this message shall be construed as an
>> offer or acceptance of any offer by Sasken Communication Technologies
>> Limited ("Sasken") unless sent with that express intent and with due
>> authority of Sasken. Sasken has taken enough
>> precautions to prevent the spread of viruses. However the company
>> accepts no liability for any damage caused by any virus transmitted by
>> this email.
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>> _______________________________________________
>> Ltp-list mailing list
>> Ltp...@li...
>> https://lists.sourceforge.net/lists/listinfo/ltp-list
SASKEN BUSINESS DISCLAIMER
This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
|