Linux NFS development
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Harry Edmon
	<harry-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org>,
	linux-nfs@vger.kernel.org,
	Max Kellermann <max-hDT0AjmEH7RAfugRpC6u6w@public.gmane.org>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] High load in 2.6.27, NFS / rpcauth_lookup_credcache()?
Date: Tue, 16 Dec 2008 15:21:16 -0800	[thread overview]
Message-ID: <20081216232116.GD6983@kroah.com> (raw)
In-Reply-To: <20081216212155.GA581-K+wRfnb2/UA@public.gmane.org>

On Tue, Dec 16, 2008 at 10:21:55PM +0100, Willy Tarreau wrote:
> On Tue, Dec 16, 2008 at 08:02:33AM -0500, Trond Myklebust wrote:
> > > and I am not using Kerberos with NFSv4 (i.e. no rpc.gssd).  Did you ever 
> > > find a solution for this problem with rpcauth_lookup_credcache?
> > 
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=23918b03060f6e572168fdde1798a905679d2e06
> 
> Trond, this should be included into next stable, right ?
> 
> It's fortunate because I know someone else who recently described me the
> same problem under the same circumstances when migrating from 2.6.22 to
> 2.6.27.

Now queued up in the 2.6.27-stable queue.

thanks,

greg k-h

      parent reply	other threads:[~2008-12-16 23:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  9:12 High load in 2.6.27, NFS / rpcauth_lookup_credcache()? Max Kellermann
     [not found] ` <20081022091207.GA12996-2pNSKKP3PSJxEiad3KpGLI/oZP4lHnOC@public.gmane.org>
2008-10-22 17:56   ` J. Bruce Fields
2008-10-23 12:36   ` Max Kellermann
2008-10-23 14:55     ` Trond Myklebust
2008-10-24  8:39       ` Max Kellermann
     [not found]         ` <20081024083913.GA15197-2pNSKKP3PSJxEiad3KpGLI/oZP4lHnOC@public.gmane.org>
2008-10-24 18:09           ` Trond Myklebust
2008-10-27  9:58             ` Max Kellermann
     [not found]               ` <20081027095843.GA10937-2pNSKKP3PSJxEiad3KpGLI/oZP4lHnOC@public.gmane.org>
2008-10-27 15:48                 ` Trond Myklebust
     [not found]                   ` <1225122503.14242.12.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-17 12:35                     ` Max Kellermann
     [not found]                       ` <20081117123536.GA16539-2pNSKKP3PSJxEiad3KpGLI/oZP4lHnOC@public.gmane.org>
2008-11-19 22:31                         ` Trond Myklebust
     [not found]                           ` <1227133861.28898.26.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-20 14:08                             ` Max Kellermann
2008-12-15 23:44       ` Harry Edmon
     [not found]         ` <4946EBFA.60700-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org>
2008-12-16 13:02           ` Trond Myklebust
     [not found]             ` <1229432553.7257.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-12-16 21:21               ` Willy Tarreau
     [not found]                 ` <20081216212155.GA581-K+wRfnb2/UA@public.gmane.org>
2008-12-16 23:21                   ` Greg KH [this message]

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=20081216232116.GD6983@kroah.com \
    --to=greg@kroah.com \
    --cc=harry-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=max-hDT0AjmEH7RAfugRpC6u6w@public.gmane.org \
    --cc=stable@kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=w@1wt.eu \
    /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