linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <kofemann@googlemail.com>
Cc: linux-nfs@vger.kernel.org, Tigran Mkrtchyan <kofemann@gmail.com>
Subject: Re: [PATH v9 00/10] handle curruent stateid
Date: Wed, 15 Feb 2012 13:55:46 -0500	[thread overview]
Message-ID: <20120215185546.GA14687@fieldses.org> (raw)
In-Reply-To: <1329170132-7081-1-git-send-email-tigran.mkrtchyan@desy.de>

On Mon, Feb 13, 2012 at 10:55:22PM +0100, Tigran Mkrtchyan wrote:
> From: Tigran Mkrtchyan <kofemann@gmail.com>
> 
> With Benny's comments.
> 
> This is ready-to-go patch set. Rebased to Bruce's nfsd-next.

All applied.  Thanks again, Tigran!

--b.

> 
> Implemented for:
> 
>  OPEN
>  OPENDOWNGRADE
>  CLOSE
>  LOCK
>  LOCKU
>  DELEGRETURN
>  FREE_STATEID
>  SETATTR
>  READ
>  WRITE
>  SAVEFH
>  RESTOREFH
>  PUTFH
>  PUTROOTFH
>  PUTPUBFH
>  LOOKUP
>  CREATE
> 
> 
> Coresponding pynfs test already submited.
> 
> Tigran.
> Tigran Mkrtchyan (10):
>   nfsd4: initialize current stateid at compile time
>   nfsd41: handle current stateid in open and close
>   nfsd41: handle current stateid on lock and locku
>   nfsd41: consume current stateid on read and write
>   nfsd41: mark PUTFH, PUTPUBFH and PUTROOTFH to clear current stateid
>   nfsd41: save and restore current stateid with current fh
>   nfsd41: mark LOOKUP, LOOKUPP and CREATE to invalidate current stateid
>   nfsd41: handle current stateid in SETATTR and FREE_STATEID
>   nfsd41: consume current stateid on DELEGRETURN and OPENDOWNGRADE
>   nfsd41: use current stateid by value
> 
>  fs/nfsd/current_stateid.h |   28 ++++++++++++
>  fs/nfsd/nfs4proc.c        |   61 +++++++++++++++++++++----
>  fs/nfsd/nfs4state.c       |  107 ++++++++++++++++++++++++++++++++++++++++++++-
>  fs/nfsd/xdr4.h            |   11 +++++
>  4 files changed, 196 insertions(+), 11 deletions(-)
>  create mode 100644 fs/nfsd/current_stateid.h
> 
> -- 
> 1.7.7.6
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" 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:[~2012-02-15 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 21:55 [PATH v9 00/10] handle curruent stateid Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 01/10] nfsd4: initialize current stateid at compile time Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 02/10] nfsd41: handle current stateid in open and close Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 03/10] nfsd41: handle current stateid on lock and locku Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 04/10] nfsd41: consume current stateid on read and write Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 05/10] nfsd41: mark PUTFH, PUTPUBFH and PUTROOTFH to clear current stateid Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 06/10] nfsd41: save and restore current stateid with current fh Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 07/10] nfsd41: mark LOOKUP, LOOKUPP and CREATE to invalidate current stateid Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 08/10] nfsd41: handle current stateid in SETATTR and FREE_STATEID Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 09/10] nfsd41: consume current stateid on DELEGRETURN and OPENDOWNGRADE Tigran Mkrtchyan
2012-02-13 21:55 ` [PATH v9 10/10] nfsd41: use current stateid by value Tigran Mkrtchyan
2012-02-15 18:55 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-13 21:54 [PATH v9 00/10] handle curruent stateid Tigran Mkrtchyan

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=20120215185546.GA14687@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kofemann@gmail.com \
    --cc=kofemann@googlemail.com \
    --cc=linux-nfs@vger.kernel.org \
    /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).