Date: Mon, 21 Feb 2011 20:32:39 +0100
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: eparis@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] fsnotify: decouple mark lock and marks fsobject
	lock
Message-ID: <20110221193239.GA32356@lsanfilippo.unix.rd.tt.avira.com>
References: <1298306349-6396-1-git-send-email-LinoSanfilippo@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1298306349-6396-1-git-send-email-LinoSanfilippo@gmx.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 752
Lines: 22


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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/