Hi, I am getting a strange problem where locks are denied by NFSv3 server even though no locks on same file where taken. While looking at the code it seems like NLM compares a lock by using "pid" and other options like form - to file offset, type of lock etc. But we are interested in "pid" because other comparison can be same for different file_locks. As we know posix threads use tgid as pid for all its thread hence NFSv3 server will can get lock request from different posix thread but with same pid. Hence NLM will treat the locking request as they are coming from same process. This may result in following problems 1. Different threads of same process can get lock on same file. 2. During "fl_grant" callback wrong "block" will be compared hence this will result in lock failure even if lock is actually granted. Is this a limitation of NLM? -- Regards, Pankaj SIngh Phone No: 8826266889 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
