public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: stable@kernel.org, linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [stable] nfsd changes for 2.6.34
Date: Tue, 30 Mar 2010 13:03:20 -0700	[thread overview]
Message-ID: <20100330200320.GB1693@kroah.com> (raw)
In-Reply-To: <20100330144054.GD11545@fieldses.org>

On Tue, Mar 30, 2010 at 10:40:54AM -0400, J. Bruce Fields wrote:
> On Mon, Mar 29, 2010 at 11:24:43AM -0700, Greg KH wrote:
> > On Wed, Mar 24, 2010 at 10:24:14AM -0400, J. Bruce Fields wrote:
> > > On Sat, Mar 06, 2010 at 12:52:12PM -0500, bfields wrote:
> > > > Please pull the following nfsd changes from the 'nfsd' branch at:
> > > > 
> > > >   git://linux-nfs.org/~bfields/linux.git for-2.6.34 nfsd
> > > > 
> > > > This is an unusually quiet cycle for the NFS server--bugfixes, some IPv6
> > > > progress, and one new export operation to improve sync performance.
> > > > 
> > > > One exception to the 'mostly quiet' statement was a regression in the
> > > > rpc code which hit a lot of people: enormous thanks to Neil for tracking
> > > > that down.
> > > 
> > > However, I forgot to Cc stable on all of those.  Stable people, could
> > > you also take the following three commits?:
> > > 
> > > 	f5822754ea006563e1bf0a1f43faaad49c0d8bb2 Revert "sunrpc: fix
> > > 	peername failed on closed listener"
> > > 	1b644b6e6f6160ae35ce4b52c2ca89ed3e356e18 Revert "sunrpc: move
> > > 	the close processing after do recvfrom method"
> > > 	301e99ce4a2f42a317129230fd42e6cd874c64b0 nfsd: ensure sockets
> > > 	are closed on error
> > > 
> > > Let me know if you need more information.
> > 
> > I've queued all of these up for the .33 -stable tree.  If any of them
> > need to go into .32 (maybe that last one?), please let me know.
> 
> Thanks; .32 needs all three of those.

Ok, care to backport them and send them to stable@kernel.org?  They
don't all apply cleanly from what I can see.

thanks,

greg k-h

  reply	other threads:[~2010-03-30 20:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06 17:52 nfsd changes for 2.6.34 J. Bruce Fields
2010-03-24 14:24 ` J. Bruce Fields
2010-03-29 18:24   ` [stable] " Greg KH
2010-03-30 14:40     ` J. Bruce Fields
2010-03-30 20:03       ` Greg KH [this message]
2010-03-31 19:30         ` J. Bruce Fields
2010-03-31 19:47           ` [PATCH] nfsd4: don't try to map gid's in generic rpc code J. Bruce Fields
2010-04-21 22:50           ` [stable] nfsd changes for 2.6.34 Greg KH
2010-04-21 23:41             ` 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=20100330200320.GB1693@kroah.com \
    --to=greg@kroah.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@kernel.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