From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: NFS4 crack Date: Tue, 20 Sep 2005 05:49:08 -0700 Message-ID: <20050920124908.GA30842@kroah.com> References: <20050918102100.GA23463@lst.de> <20050918143615.GA3428@fieldses.org> <20050919103547.GA8998@lst.de> <20050919203143.GC26122@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , akpm@osdl.org, neilb@cse.unsw.edu.au, andros@citi.umich.edu, linux-fsdevel@vger.kernel.org Return-path: Received: from mail.kroah.org ([69.55.234.183]:1244 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S965002AbVITMtm (ORCPT ); Tue, 20 Sep 2005 08:49:42 -0400 To: "J. Bruce Fields" Content-Disposition: inline In-Reply-To: <20050919203143.GC26122@fieldses.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Sep 19, 2005 at 04:31:43PM -0400, J. Bruce Fields wrote: > We'd need two pieces of user<->kernel interface: > > 1. An upcall to userspace to tell it about new client state. We > also need to be able to wait for userspace to commit something > to disk, as the information has to survive a reboot. > 2. A way for userspace to dump recorded state to the kernel the > next time nfsd starts up. > > Number 1 could be done with something like hotplug, I guess. (It can be > told to wait for the userspace helper to exit, right?) Well, calling /sbin/hotplug itself can't be told to wait, especially as that value is being set to NULL by most distros these days, as they are using netlink instead. Good luck, greg k-h