linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lin Ming <lin@ming.vg>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
	Serge Hallyn <serge@hallyn.com>,
	Matt Helsley <matthltc@us.ibm.com>, Dan Smith <danms@us.ibm.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Jamie Lokier <jamie@shareable.org>,
	Steven Whitehouse <swhiteho@redhat.com>,
	linux-fsdevel@vger.kernel.org,
	Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH 0/5][v5][cr] Checkpoint/restart file locks
Date: Fri, 29 Oct 2010 22:31:21 +0800	[thread overview]
Message-ID: <AANLkTiktKVuAtjPaHT9d+7ATpKn+jMonFYzeEmd85L3o@mail.gmail.com> (raw)
In-Reply-To: <1288333001-28838-1-git-send-email-sukadev@linux.vnet.ibm.com>

On Fri, Oct 29, 2010 at 2:16 PM, Sukadev Bhattiprolu
<sukadev@linux.vnet.ibm.com> wrote:
> Checkpoint/restart file locks.
>
> Changelog[v5]:
>        - This patchset only checkpoints/restores file locks. C/R of
>          file-owner and file-leases will be addressed in follown patches.
>          C/R of file-owner information must deal with nested-containers
>          and, will need a way to C/R struct pids. C/R of file-leases depends
>          on C/R of file-owner information.
>
>
> Sukadev Bhattiprolu (5):
>  Move file_lock macros into linux/fs.h
>  Define flock_set()
>  Define flock64_set()
>  Checkpoint/restore file-locks
>  Document design of C/R of file-locks and leases
>
>  Documentation/checkpoint/file-locks |   52 ++++++
>  fs/checkpoint.c                     |  318 +++++++++++++++++++++++++++++++++--
>  fs/locks.c                          |   89 ++++++----
>  include/linux/checkpoint_hdr.h      |   17 ++
>  include/linux/fs.h                  |   10 +
>  5 files changed, 433 insertions(+), 53 deletions(-)
>  create mode 100644 Documentation/checkpoint/file-locks

Hi,

Which tree are these patches against?

I can't apply them neither to Linus tree(18cb657c) nor
vfs-2.6.git/for-linus branch(a4cdbd8b).

Lin Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-10-29 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29  6:16 [PATCH 0/5][v5][cr] Checkpoint/restart file locks Sukadev Bhattiprolu
2010-10-29  6:16 ` [PATCH 1/5][v5][cr]: Move file_lock macros into linux/fs.h Sukadev Bhattiprolu
2010-10-29  6:16 ` [PATCH 2/5][v5][cr]: Define flock_set() Sukadev Bhattiprolu
2010-10-29  6:16 ` [PATCH 3/5][v5][cr]: Define flock64_set() Sukadev Bhattiprolu
2010-10-29  6:16 ` [PATCH 4/5][v5][cr]: Checkpoint/restore file-locks Sukadev Bhattiprolu
2010-10-29  6:16 ` [PATCH 5/5][v5][cr]: Document design of C/R of file-locks Sukadev Bhattiprolu
2010-10-29 14:31 ` Lin Ming [this message]
2010-10-29 18:35   ` [PATCH 0/5][v5][cr] Checkpoint/restart file locks Sukadev Bhattiprolu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTiktKVuAtjPaHT9d+7ATpKn+jMonFYzeEmd85L3o@mail.gmail.com \
    --to=lin@ming.vg \
    --cc=containers@lists.linux-foundation.org \
    --cc=danms@us.ibm.com \
    --cc=jamie@shareable.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=matthltc@us.ibm.com \
    --cc=orenl@cs.columbia.edu \
    --cc=serge@hallyn.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=swhiteho@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).