Linux NFS development
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Jeff Layton <jlayton@primarydata.com>, stable@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, bfields@fieldses.org
Subject: Re: [stable PATCH] nfsd: don't try to reuse an expired DRC entry off the list
Date: Wed, 25 Jun 2014 15:32:56 +0200	[thread overview]
Message-ID: <53AACF88.5000006@suse.cz> (raw)
In-Reply-To: <1403290612-15341-1-git-send-email-jlayton@primarydata.com>

On 06/20/2014 08:56 PM, Jeff Layton wrote:
> From: Jeff Layton <jlayton@redhat.com>
> 
> This is commit a0ef5e19684f0447da9ff0654a12019c484f57ca in mainline.
> 
> While the commit message below doesn't lay this out, we've subsequently
> found that there are some cases where an entry that's still in use can
> be freed prematurely if a particular operation takes a *very* long time
> (on the order of minutes) and/or the server is very busy and doesn't
> have a lot of memory dedicated to the DRC. This patch eliminates that
> possibility, so it's actually more than just a cleanup.
> 
> The regression crept in in v3.9, and this patch went into mainline in
> v3.14. Please apply this to any stable kernel between those two
> mainline releases.

Now applied to 3.12. Thanks.


-- 
js
suse labs

  parent reply	other threads:[~2014-06-25 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 18:56 [stable PATCH] nfsd: don't try to reuse an expired DRC entry off the list Jeff Layton
2014-06-20 18:59 ` J. Bruce Fields
2014-06-25 13:32 ` Jiri Slaby [this message]
2014-06-25 13:36   ` Jeff Layton
2014-06-26 13:23     ` Luis Henriques

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=53AACF88.5000006@suse.cz \
    --to=jslaby@suse.cz \
    --cc=bfields@fieldses.org \
    --cc=jlayton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@vger.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