linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tigran Mkrtchyan <kofemann@googlemail.com>
To: linux-nfs@vger.kernel.org
Cc: Tigran Mkrtchyan <kofemann@gmail.com>
Subject: [PATH v6 0/9] handle curruent stateid
Date: Sun, 15 Jan 2012 17:20:01 +0100	[thread overview]
Message-ID: <1326644410-7482-1-git-send-email-tigran.mkrtchyan@desy.de> (raw)

From: Tigran Mkrtchyan <kofemann@gmail.com>


This is ready-to-go patch set. Rebased to Bruce's nfsd-next.

Implemented for:

  OPEN
  OPENDOWNGRADE 
  CLOSE
  LOCK
  LOCKU
  DELEGRETURN
  FREE_STATEID
  SETATTR
  READ
  WRITE
  SAVEFH
  RESTOREFH
  PUTFH
  PUTROOTFH
  PUTPUBFH
  LOOKUP
  CREATE 

PNFS released patches will be submitted as soon as patches will be merged with Benny's tree.

I will clean-up and submit corresponding pynfs test later today or tomorrow.

Comments and suggestions are welcome

Tigran.

Tigran Mkrtchyan (9):
  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

 fs/nfsd/current_stateid.h |   27 ++++++++++++
 fs/nfsd/nfs4proc.c        |   55 ++++++++++++++++++++-----
 fs/nfsd/nfs4state.c       |   99 ++++++++++++++++++++++++++++++++++++++++++++-
 fs/nfsd/xdr4.h            |    2 +
 4 files changed, 172 insertions(+), 11 deletions(-)
 create mode 100644 fs/nfsd/current_stateid.h

-- 
1.7.7.5


             reply	other threads:[~2012-01-15 16:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 16:20 Tigran Mkrtchyan [this message]
2012-01-15 16:20 ` [PATH v6 1/9] nfsd4: initialize current stateid at compile time Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 2/9] nfsd41: handle current stateid in open and close Tigran Mkrtchyan
2012-01-17 19:40   ` J. Bruce Fields
2012-01-17 19:43     ` J. Bruce Fields
2012-01-17 20:14     ` Tigran Mkrtchyan
2012-01-17 20:45       ` J. Bruce Fields
2012-01-17 21:17         ` Tiramisu Mokka
2012-01-15 16:20 ` [PATH v6 3/9] nfsd41: handle current stateid on lock and locku Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 4/9] nfsd41: consume current stateid on read and write Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 5/9] nfsd41: mark PUTFH, PUTPUBFH and PUTROOTFH to clear current stateid Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 6/9] nfsd41: save and restore current stateid with current fh Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 7/9] nfsd41: mark LOOKUP, LOOKUPP and CREATE to invalidate current stateid Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 8/9] nfsd41: handle current stateid in SETATTR and FREE_STATEID Tigran Mkrtchyan
2012-01-15 16:20 ` [PATH v6 9/9] nfsd41: consume current stateid on DELEGRETURN and OPENDOWNGRADE 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=1326644410-7482-1-git-send-email-tigran.mkrtchyan@desy.de \
    --to=kofemann@googlemail.com \
    --cc=kofemann@gmail.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).