From: Jiri Slaby <jslaby@suse.cz>
To: Jeff Layton <jlayton@primarydata.com>, stable@vger.kernel.org
Cc: kasparek@fit.vutbr.cz, linux-nfs@vger.kernel.org, bfields@fieldses.org
Subject: Re: [stable PATCH] nfsd: don't halt scanning the DRC LRU list when there's an RC_INPROG entry
Date: Wed, 25 Jun 2014 15:54:20 +0200 [thread overview]
Message-ID: <53AAD48C.7090401@suse.cz> (raw)
In-Reply-To: <1403704114-3536-1-git-send-email-jlayton@primarydata.com>
On 06/25/2014 03:48 PM, Jeff Layton wrote:
> The patch below has already made it into mainline as commit
> 1b19453d1c6abcfa7c312ba6c9f11a277568fc94. I think we need it in stable
> as well. In addition to making the cache pruner more efficient, it also
> fixes a logic bug in prune_cache_entries. If num_drc_entries is greater
> than the max, then we can end up freeing the entry even if it's still
> RC_INPROG. This patch ensures that RC_INPROG entries are always skipped
> and that prevents a use-after-free.
>
> Please apply this to any stable kernel, v3.9 or above. Original patch
> description follows.
Pushed to 3.12 too. Thanks.
--
js
suse labs
prev parent reply other threads:[~2014-06-25 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 13:48 [stable PATCH] nfsd: don't halt scanning the DRC LRU list when there's an RC_INPROG entry Jeff Layton
2014-06-25 13:54 ` Jiri Slaby [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=53AAD48C.7090401@suse.cz \
--to=jslaby@suse.cz \
--cc=bfields@fieldses.org \
--cc=jlayton@primarydata.com \
--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