From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Changing inode_operations Date: 4 Mar 2003 14:55:03 -0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id OAA32503 for ; Tue, 4 Mar 2003 14:55:18 -0800 Received: from palladium.transmeta.com (palladium.transmeta.com [10.0.0.117]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id h24Mt5F27999 for ; Tue, 4 Mar 2003 14:55:05 -0800 (PST) Received: (from mail@localhost) by palladium.transmeta.com (8.9.3/8.9.3) id OAA00548 for linux-fsdevel@vger.kernel.org; Tue, 4 Mar 2003 14:55:04 -0800 To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi all, Does anyone know if there are any filesystems which change the inode_operations on a directory after the directory inode has already been instantiated? I'm still hunting for a reasonable way to do autofs tree mounts without atomicity problems... -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64