public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
	nfsv4@linux-nfs.org, Neil Brown <neilb@suse.de>
Subject: nfsd updates for 2.6.24
Date: Sun, 14 Oct 2007 20:04:05 -0400	[thread overview]
Message-ID: <20071015000405.GD31260@fieldses.org> (raw)

You can pull the following nfs server changes from

  git://linux-nfs.org/~bfields/linux.git nfs-server-stable

Nothing earth-shaking this time; mainly small bugfixes and cleanups.

--b.

Andrew Morton (1):
      nfsd warning fix

Christoph Hellwig (1):
      nfsd: fix horrible indentation in nfsd_setattr

Dr. David Alan Gilbert (1):
      knfsd: Add source address to sunrpc svc errors

J. Bruce Fields (15):
      nfsd: tone down inaccurate dprintk
      nfsd: remove unused cache_for_each macro
      knfsd: delete code made redundant by map_new_errors
      knfsd: cleanup of nfsd4 cmp_* functions
      knfsd: demote some printk()s to dprintk()s
      knfsd: nfs4 name->id mapping not correctly parsing negative downcall
      knfsd: spawn kernel thread to probe callback channel
      knfsd: move nfsv4 slab creation/destruction to module init/exit
      knfsd: fix callback rpc cred
      knfsd: remove code duplication in nfsd4_setclientid()
      svcgss: move init code into separate function
      knfsd: let nfsd manage timing out its own leases
      knfsd: don't shutdown callbacks until nfsv4 client is freed
      knfsd: nfsv4 delegation recall should take reference on client
      knfsd: query filesystem for NFSv4 getattr of FATTR4_MAXNAME

Peter Staubach (1):
      knfsd: 64 bit ino support for NFS server

 fs/nfsd/nfs3xdr.c                 |   59 +++++------
 fs/nfsd/nfs4callback.c            |   89 +++++------------
 fs/nfsd/nfs4idmap.c               |    8 +-
 fs/nfsd/nfs4proc.c                |    4 +-
 fs/nfsd/nfs4state.c               |  200 +++++++++++++++++-------------------
 fs/nfsd/nfs4xdr.c                 |   22 ++--
 fs/nfsd/nfsctl.c                  |    7 +-
 fs/nfsd/nfssvc.c                  |    8 +-
 fs/nfsd/nfsxdr.c                  |    4 +
 fs/nfsd/vfs.c                     |   43 +++++---
 include/linux/nfsd/nfsd.h         |   18 ++--
 include/linux/nfsd/nfsfh.h        |   42 +-------
 include/linux/nfsd/xdr4.h         |    4 +-
 include/linux/sunrpc/cache.h      |   10 --
 net/sunrpc/auth_gss/svcauth_gss.c |  144 ++++++++++++++------------
 net/sunrpc/svc.c                  |   40 ++++++--
 16 files changed, 326 insertions(+), 376 deletions(-)

                 reply	other threads:[~2007-10-15  0:04 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=20071015000405.GD31260@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.org \
    --cc=torvalds@linux-foundation.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