From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: NFS4 crack Date: Wed, 21 Sep 2005 00:44:03 -0700 Message-ID: <20050921004403.23f3fbda.akpm@osdl.org> References: <20050918102100.GA23463@lst.de> <17200.22256.314596.486248@cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hch@lst.de, andros@citi.umich.edu, bfields@citi.umich.edu, linux-fsdevel@vger.kernel.org, okir@suse.de Return-path: Received: from smtp.osdl.org ([65.172.181.4]:11227 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1750710AbVIUHow (ORCPT ); Wed, 21 Sep 2005 03:44:52 -0400 To: Neil Brown In-Reply-To: <17200.22256.314596.486248@cse.unsw.edu.au> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Neil Brown wrote: > > Now, this in-kernel-application needs to store stable > application-specific data somewhere. May it: > > 1/ open a directory and create files in it and write to them > 2/ open a directory and create files provided that the name of the > directory is given by userspace > 3/ create files in a directory that was created by userspace and > given to the knfsd application as a filedescriptor > 4/ write data to files which were created and opened by used-space > based on filenames provided by knfsd (hostnames or equivalents in > this case). > 5/ pass the data to userspace and let it worry completely. > 6/ sorry, you cannot have application-specific state. > 5/ sounds good. There are numerous options, newly including connector and configfs.