From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Subject: Re: [PATCH 00/16][cr][v3]: C/R file owner, locks, leases
Date: Wed, 4 Aug 2010 12:01:12 -0700
Message-ID: <20100804190112.GA11571@us.ibm.com>
References: <1280877097-12377-1-git-send-email-sukadev@linux.vnet.ibm.com> <1280918720.2566.18.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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: Steven Whitehouse <swhiteho@redhat.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from e39.co.us.ibm.com ([32.97.110.160]:36439 "EHLO
	e39.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1758022Ab0HDSz4 (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 4 Aug 2010 14:55:56 -0400
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226])
	by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id o74Ik5kM016373
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Aug 2010 12:46:05 -0600
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o74IthLl129930
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Aug 2010 12:55:44 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o74ItdhQ002752
	for <linux-fsdevel@vger.kernel.org>; Wed, 4 Aug 2010 12:55:42 -0600
Content-Disposition: inline
In-Reply-To: <1280918720.2566.18.camel@localhost>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Steven Whitehouse [swhiteho@redhat.com] wrote:
| 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?

Well, there is no document atm and I tried to explain how it is supposed
to work in the patches that restart file-locks (patches 4. 9, 16).

| 
| 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?

But I see that your question is about the bigger picture. Given that
this question was asked on the previous version of the patchset, I will
add a FAQ/description in patch 0 next time.

For now, please see:

	http://marc.info/?l=linux-fsdevel&m=127657580718791&w=2

Thanks,

Sukadev