Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail2.shareable.org ([80.68.89.115]:41339 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753123Ab1KWAbA (ORCPT ); Tue, 22 Nov 2011 19:31:00 -0500 Date: Wed, 23 Nov 2011 00:30:57 +0000 From: Jamie Lokier To: "J. Bruce Fields" Cc: Volker Lendecke , linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, samba-technical@lists.samba.org, Casey Bodley Subject: Re: [PATCH] locks: breaking read lease should not block read open Message-ID: <20111123003057.GA2385@jl-vm1.vm.bytemark.co.uk> References: <20110609231606.GB22215@fieldses.org> <20110610134859.GA27837@fieldses.org> <20110721000758.GD27871@fieldses.org> <20110819190829.GD11512@jl-vm1.vm.bytemark.co.uk> <20110821165029.GA9296@fieldses.org> <20111121124650.GA12942@jl-vm1.vm.bytemark.co.uk> <20111122214441.GB23243@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20111122214441.GB23243@fieldses.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: J. Bruce Fields wrote: > > Fyi, fanotify is also synchronous: > > Oh, I didn't know that, apologies for the confusion. > > > It blocks the conflicting operation > > until the fanotify-using application allows it to proceed - or > > alternatively it can prevent the conflicting operating from proceeding > > at all. > > Just grepping for "fsnotify" (which fanotify is built on?) I find a lot > of hooks in the vfs that all appear to have void returns and to be > called after the operation is done. How does it fail an operation? No > doubt I'm missing something. The hook is fsnotify_perm(), called in security/security.c. -- Jamie