From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Boyer Subject: Re: [RFC] Support for stackable file systems on top of nfs Date: Thu, 10 Nov 2005 17:30:29 -0800 Message-ID: <20051111013029.GA3768@pants.nu> References: <1131662421.8804.30.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Trond Myklebust , fsdevel , nfsv4 , Dave Kleikamp , Shaya Potter Return-path: Received: from adsl-216-102-214-42.dsl.snfc21.pacbell.net ([216.102.214.42]:36626 "EHLO cynthia.pants.nu") by vger.kernel.org with ESMTP id S1751229AbVKKBab (ORCPT ); Thu, 10 Nov 2005 20:30:31 -0500 To: Bryan Henderson Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Nov 10, 2005 at 04:12:25PM -0800, Bryan Henderson wrote: > Why are credentials cached in the struct file? Is that a natural > place for it or just what's available? I don't have intimate knowledge of the details, but I suspect it's because credentials more naturally map onto a file than an inode. For example, if you have two users opening the exact same path from an NFS mount, there is just one struct inode, but there are at least two different struct file (one for each open call). The credentials are tied to the user session, not to the path. Because of this, you may have multiple unrelated credentials associated with what is the same struct inode under the covers. Brad Boyer flar@allandria.com