Re: [PATCH 0/5] fsnotify: decouple mark lock and marks fsobject lock

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

 



The intro was somehow truncated. It should be:

This patch series removes the dependency between holding the lock of a mark and 
holding the lock of the marks fsobject (inode/vfsmount). 
Right now we have to use the following locking order

1. mark lock
2. inode/vfsmount lock

With these patches only one of both locks are taken at the same time, which 
removes the need for a strict locking order.

These patches depend on patch "inotify: fix race when adding a new watch" sent to lkml
on Feb. 11.

Lino
--
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