mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [BK] NFS client updates for 2.5.67
Date: Tue, 8 Apr 2003 03:20:26 +0200	[thread overview]
Message-ID: <16018.9178.354140.998203@charged.uio.no> (raw)

Linus, please do a

	bk pull http://nfsclient.bkbits.net/linux-2.5

This will update the following files:

 fs/nfs/Makefile           |    3 
 fs/nfs/dir.c              |   23 +
 fs/nfs/file.c             |   27 +
 fs/nfs/idmap.c            |  474 ++++++++++++++++++++++++++++++++++
 fs/nfs/inode.c            |   38 +-
 fs/nfs/nfs4proc.c         |  535 ++++++++++++++++++++++++++-------------
 fs/nfs/nfs4state.c        |  178 +++++++++++-
 fs/nfs/nfs4xdr.c          |  630 ++++++++++++++++++++++++++++++----------------
 include/linux/nfs4.h      |    4 
 include/linux/nfs_fs.h    |   73 ++++-
 include/linux/nfs_fs_sb.h |    1 
 include/linux/nfs_idmap.h |   69 +++++
 include/linux/nfs_xdr.h   |   77 +++++
 net/sunrpc/xprt.c         |   10 
 14 files changed, 1718 insertions(+), 424 deletions(-)

through these ChangeSets:

<marius@citi.umich.edu> (03/04/08 1.1054)
   Add hooks into the NFSv4 XDR code to make use of the new uid/gid
   mapper upcall mechanism.

<marius@citi.umich.edu> (03/04/08 1.1053)
   Add support for mapping NFSv4 remote user/group names into local
   unix-style uid/gids.
   
   Note that this makes use of the RPC client upcall mechanism
   (rpc_pipefs) to notify a userland daemon that does the actual mapping.
   The results are then cached in the kernel.
   The userland daemon can be downloaded from the CITI NFSv4 page at
   
        http://www.citi.umich.edu/projects/nfsv4/

<trond.myklebust@fys.uio.no> (03/04/08 1.1052)
   Make the NFSv4 write code use the stateid if it exists.

<trond.myklebust@fys.uio.no> (03/04/08 1.1051)
   Make NFSv4 'read' code use the cached stateid if it exists.

<trond.myklebust@fys.uio.no> (03/04/08 1.1050)
   Make NFSv4 'setattr()' method use the cached stateid if the file is
   already open.

<trond.myklebust@fys.uio.no> (03/04/08 1.1049)
   Setup code to tear down the NFSv4 state once we're done with a file.

<trond.myklebust@fys.uio.no> (03/04/08 1.1048)
   Implement stateful open() for NFSv4 as per RFC3010-bis.
   The resulting state is saved in the NFS-specific part of the
   struct inode.
   
   Initially we just start with 3 possible states:
     - open for read
     - open for write
     - open for read/write

<trond.myklebust@fys.uio.no> (03/04/08 1.1047)
   Prepare for the introduction of NFSv4 state code.
   
   Split out the open() method for regular files from that of
   directories.

<trond.myklebust@fys.uio.no> (03/04/08 1.1046)
   Remove bogus check on the size of NFSv4 'readdir' cookies.

<trond.myklebust@fys.uio.no> (03/04/08 1.1045)
   Fix a series of NFS read/readdir/readlink errors.
   
   Tightens consistency checks on the process of reading the reply skb in
   the SunRPC client. Reject a reply if we didn't succeed in reading the
   entire skb.


                 reply	other threads:[~2003-04-08  1:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=16018.9178.354140.998203@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®