From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [PATCH 00/16][cr][v3]: C/R file owner, locks, leases
Date: Wed, 04 Aug 2010 11:45:20 +0100
Message-ID: <1280918720.2566.18.camel@localhost>
References: <1280877097-12377-1-git-send-email-sukadev@linux.vnet.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Oren Laadan <orenl@cs.columbia.edu>,
	Serge Hallyn <serge@hallyn.com>,
	Matt Helsley <matthltc@us.ibm.com>,
	Dan Smith <danms@us.ibm.com>,
	John Stultz <johnstul@us.ibm.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Jamie Lokier <jamie@shareable.org>,
	linux-fsdevel@vger.kernel.org,
	Containers <containers@lists.linux-foundation.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:32573 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1757105Ab0HDKkm (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 4 Aug 2010 06:40:42 -0400
In-Reply-To: <1280877097-12377-1-git-send-email-sukadev@linux.vnet.ibm.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Hi,

On Tue, 2010-08-03 at 16:11 -0700, Sukadev Bhattiprolu wrote:
> Checkpoint/restart file owner, file-locks and file-lease information.
> 
Can you explain roughly how this is intended to work, or point me at a
document explaining it?

I'm trying to figure out how the file lock checkpoint will work with
cluster filesystems, or if there needs to be a mechanism to turn this
feature off for those filesystems. What prevents the lock state changing
in an incompatible way between the checkpoint and the restore?

Steve.