Re: [PATCH 2/4] locks: don't unnecessarily fail posix lock operations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > In the first case no new locks are needed.  In the second, no locks
> > are modified prior to the check.
> 
> Consider something like
> 
> fcntl(SETLK, 0, 100)
> fcntl(SETLK, 0, 100)
> fcntl(SETLK, 0, 100)

Huh?  What is the type of lock in each case.

But anyway your example is no good.  If the new lock completely covers
the previous one, then the old lock will simply be adjusted and no new
lock is inserted.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux