From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: FMODE_EXEC or alike? Date: Tue, 21 Feb 2006 03:36:05 -0800 Message-ID: <20060221033605.1518ceab.akpm@osdl.org> References: <20060220221948.GC5733@linuxhacker.ru> <20060220215122.7aa8bbe5.akpm@osdl.org> <20060221113055.GF5733@linuxhacker.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from smtp.osdl.org ([65.172.181.4]:23488 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932694AbWBULhp (ORCPT ); Tue, 21 Feb 2006 06:37:45 -0500 To: Oleg Drokin In-Reply-To: <20060221113055.GF5733@linuxhacker.ru> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Oleg Drokin wrote: > > Introduce FMODE_EXEC file flag, to indicate that file is being opened for > execution. This is useful for distributed filesystems to maintain consistent > behavior for returning ETXTBUSY when opening for write and execution > happens on different nodes. You forgot something. Are other clustered/distributed filesystems likely to need something like this and if so, is this implementation sufficient for their purposes?