Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751250AbVJFRZx (ORCPT ); Thu, 6 Oct 2005 13:25:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751247AbVJFRZx (ORCPT ); Thu, 6 Oct 2005 13:25:53 -0400 Received: from pat.uio.no ([129.240.130.16]:43909 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S1751246AbVJFRZw (ORCPT ); Thu, 6 Oct 2005 13:25:52 -0400 Subject: Re: [RFC] atomic create+open From: Trond Myklebust To: Miklos Szeredi Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org In-Reply-To: References: <1128616864.8396.32.camel@lade.trondhjem.org> Content-Type: text/plain Date: Thu, 06 Oct 2005 13:25:26 -0400 Message-Id: <1128619526.16534.8.camel@lade.trondhjem.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-3.929, required 12, autolearn=disabled, AWL 1.07, UIO_MAIL_IS_INTERNAL -5.00) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 786 Lines: 20 to den 06.10.2005 Klokka 19:06 (+0200) skreiv Miklos Szeredi: > > The reason why we do it as a lookup intent is because this has to be > > atomic lookup+create+open in order to be at all useful to NFS. > > Oh, and btw there's a problem with atomic lookup+create+open: mounts. > Do you want to follow mounts inside ->lookup(). Ugly. No. Why do you think you would need to? The VFS is supposed to protect you against races with mount and other local objects (dcache races, inode races,...). The problem is remote objects. Cheers, Trond - 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/