2002-04-08 11:03:12

by Dumas Patrice

[permalink] [raw]
Subject: lockd bug (?)

Hi,

I send a message before but nobody answered. I made some tests, they seem to
prove what I said. What did I say ? A blocked lock is never deleted and lockd
continues sending granted callbacks, even when the client responded to the
callback.

Here is my test:

Everything is on zeus, I mounted a filesystem locally:

mount zeus:/cired/zeus/home /mnt/tmp

Then I use the testlk from nfs-utils:

[[email protected] locktest]$ ./testlk /mnt/tmp/dumas/testlock
fcntl: ok

In another terminal I reuse ./testlk to have a blocked lock:
[[email protected] locktest]$ ./testlk /mnt/tmp/dumas/testlock -b

Then I do a ctrl-C on the first terminal, I get
[[email protected] locktest]$ ./testlk /mnt/tmp/dumas/testlock
fcntl: ok

[[email protected] locktest]$

Then on the second terminal, the lock is granted and thus I get
[[email protected] locktest]$ ./testlk /mnt/tmp/dumas/testlock -b
fcntl: ok

I don't stop that one, because my point is that now lockd will keep on sending
unneeded callbacks, because it does nothing with the responses of the client. I
attached the dmesg output. I commented it a bit with #comment


Attachments:
(No filename) (1.10 kB)
dmesg (2.62 kB)
Download all attachments