From: Jeff Layton <jeff.layton@primarydata.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org, linux-nfs@vger.kernel.org,
bfields@fieldses.org, Tomas Kasparek <kasparek@fit.vutbr.cz>
Subject: Re: [stable PATCH] nfsd: don't try to reuse an expired DRC entry off the list
Date: Wed, 25 Jun 2014 09:36:32 -0400 [thread overview]
Message-ID: <20140625093632.0d7b58ac@tlielax.poochiereds.net> (raw)
In-Reply-To: <53AACF88.5000006@suse.cz>
On Wed, 25 Jun 2014 15:32:56 +0200
Jiri Slaby <jslaby@suse.cz> wrote:
> 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.
>
>
Thank you! It also turns out that we're going to want to pull
1b19453d1c6abcfa7c312ba6c9f11a277568fc94 from mainline into stable
kernels as well. There's one more possibility for an entry to be freed
while still in use that that patch will fix.
I'll resend that to stable@vger later today...
Thanks!
--
Jeff Layton <jlayton@primarydata.com>
next prev parent reply other threads:[~2014-06-25 13:36 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
2014-06-25 13:36 ` Jeff Layton [this message]
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=20140625093632.0d7b58ac@tlielax.poochiereds.net \
--to=jeff.layton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=jslaby@suse.cz \
--cc=kasparek@fit.vutbr.cz \
--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