From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: which dentry a page belongs to Date: Fri, 23 Apr 2004 22:37:47 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040423213747.GA8915@mail.shareable.org> References: <1082732223.1943.11.camel@zaphod> <20040423151458.GC6300@mail.shareable.org> <1082734938.1943.26.camel@zaphod> <20040423173738.A3812@infradead.org> <1082739174.1943.49.camel@zaphod> <20040423180130.A4255@infradead.org> <1082740707.1943.61.camel@zaphod> <20040423173719.GB7335@mail.shareable.org> <1082743539.1943.84.camel@zaphod> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , linux-fsdevel@vger.kernel.org Return-path: Received: from mail.shareable.org ([81.29.64.88]:41638 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S261498AbUDWVh4 (ORCPT ); Fri, 23 Apr 2004 17:37:56 -0400 To: Shaya Potter Content-Disposition: inline In-Reply-To: <1082743539.1943.84.camel@zaphod> List-Id: linux-fsdevel.vger.kernel.org Shaya Potter wrote: > right, I know i can do that (or on lookup(), or on open() ) but that > basically limits me to a open/close transaction for versioning. Can't > ioctl the fs, and cause all future writes to be in a new version. "all future writes" is not very well defined with shared writable mappings. Imagine this: 1. program write to a page, dirty bit is set in pte [6 weeks later...] 2. you do the ioctl 3. your writepage gets called Now you will store an update for a change which happened 6 weeks before you called the ioctl(). Is that what you really wanted? Perhaps it is. -- Jamie