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

[Lino Sanfilippo]

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-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/