public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: stable@kernel.org
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Neil Brown <neilb@suse.de>, Marc Eshel <eshel@almaden.ibm.com>
Subject: Re: nfsd fixes for 2.6.29
Date: Tue, 27 Jan 2009 18:23:04 -0500	[thread overview]
Message-ID: <20090127232304.GD13854@fieldses.org> (raw)
In-Reply-To: <20090127232058.GC13854@fieldses.org>

On Tue, Jan 27, 2009 at 06:20:58PM -0500, bfields wrote:
> The following changes are available in the git repository at:
> 
>   git://linux-nfs.org/~bfields/linux.git for-2.6.29
> 
> Mainly three regression fixes, but I also snuck in two minor
> documentation updates.  (I can stop that if it's annoying.)
> 
> --b.
> 
> J. Bruce Fields (3):
>       nfs: note that CONFIG_SUNRPC_XPRT_RDMA turns on server side support too
>       nfsd: fix null dereference on error path
>       nfsd: fix cred leak on every rpc
> 
> James Lentini (1):
>       update port number in NFS/RDMA documentation
> 
> Jeff Layton (1):
>       nfsd: only set file_lock.fl_lmops in nfsd4_lockt if a stateowner is found

Jeff's patch (together with the previous patch it fixes) are also
appropriate for stable; I'll follow up with the patches in question.

--b.

  reply	other threads:[~2009-01-27 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 23:20 nfsd fixes for 2.6.29 J. Bruce Fields
2009-01-27 23:23 ` J. Bruce Fields [this message]
2009-01-27 23:25   ` [PATCH] nfsd: Ensure nfsv4 calls the underlying filesystem on LOCKT J. Bruce Fields
2009-01-27 23:26     ` [PATCH] nfsd: only set file_lock.fl_lmops in nfsd4_lockt if a stateowner is found J. Bruce Fields

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=20090127232304.GD13854@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=eshel@almaden.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=stable@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