public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kasparek Tomas <kasparek@fit.vutbr.cz>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [stable] NFS client packet storm on 2.6.27.x
Date: Mon, 13 Jul 2009 10:20:01 -0700	[thread overview]
Message-ID: <20090713172001.GA22775@kroah.com> (raw)
In-Reply-To: <20090713111214.GC30754@fit.vutbr.cz>

On Mon, Jul 13, 2009 at 01:12:15PM +0200, Kasparek Tomas wrote:
> On Thu, Jun 25, 2009 at 07:55:32AM +0200, Kasparek Tomas wrote:
> > http://www.linux-nfs.org/Linux-2.6.x/2.6.27/
> > 
> > .../fixups_4/linux-2.6.27-001-respond_promptly_to_socket_errors.dif
> > .../fixups_4/linux-2.6.27-002-respond_promptly_to_socket_errors_2.dif
> > 
> > ...
> > Together with tcp_linger patch it seems to improve the situation a lot to
> > state when it is possible for me to use 2.6.27.x kernels.
> > 
> > Trond, will it be possible to get tcp_linger and the upper twho patches to
> > 2.6.27.x stable queue so others get these fixes?
> 
> I got no response so far, is there someone who could advise me what to do
> to get above patches to 2.6.27.x stable? Or is there some reason, why this
> is not possible at all?

Can you backport them and send them to stable@kernel.org with the git
commit ids of the orignal patches?

thanks,

greg k-h

  reply	other threads:[~2009-07-13 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1231782009.7322.12.camel@heimdal.trondhjem.org>
     [not found] ` <1231809446.7322.17.camel@heimdal.trondhjem.org>
     [not found]   ` <20090113152201.GD47559@fit.vutbr.cz>
     [not found]     ` <20090116104802.GF47559@fit.vutbr.cz>
     [not found]       ` <20090118130835.GH47559@fit.vutbr.cz>
     [not found]         ` <20090120150301.GG47559@fit.vutbr.cz>
     [not found]           ` <1232465547.7055.3.camel@heimdal.trondhjem.org>
     [not found]             ` <20090303120848.GV89843@fit.vutbr.cz>
     [not found]               ` <1236089767.9631.4.camel@heimdal.trondhjem.org>
     [not found]                 ` <20090418051739.GL64731@fit.vutbr.cz>
2009-04-22 17:27                   ` NFS client packet storm on 2.6.27.x Kasparek Tomas
2009-04-29 12:12                     ` Steve Dickson
2009-04-29 14:57                       ` Kasparek Tomas
2009-06-25  5:55                     ` Kasparek Tomas
2009-07-13 11:12                       ` Kasparek Tomas
2009-07-13 17:20                         ` Greg KH [this message]
2009-07-13 17:40                           ` [stable] " Trond Myklebust
2009-07-28 18:31                             ` Greg KH

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=20090713172001.GA22775@kroah.com \
    --to=greg@kroah.com \
    --cc=kasparek@fit.vutbr.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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