From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Vasily Averin <vvs@virtuozzo.com>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Subject: Re: [PATCH 0/1] cache_head leak in sunrpc_cache_lookup()
Date: Fri, 5 Apr 2019 19:52:41 -0400 [thread overview]
Message-ID: <20190405235241.GE8397@fieldses.org> (raw)
In-Reply-To: <87k1g9z3vj.fsf@notabene.neil.brown.name>
On Fri, Apr 05, 2019 at 11:34:40AM +1100, NeilBrown wrote:
> On Fri, Apr 05 2019, NeilBrown wrote:
> >
> > Unfortunately I was wrong. See below.
> >
>
> Arrghh.. Ignore that patch. Use this one.
Took me a moment to spot the difference. OK! Queuing that up for
5.1....
--b.
>
> NeilBrown
>
> From b7a8dced1a34869710a5d68a64e8bd37bf2ab426 Mon Sep 17 00:00:00 2001
> From: NeilBrown <neilb@suse.com>
> Date: Fri, 5 Apr 2019 09:04:41 +1100
> Subject: [PATCH] sunrpc: don't mark uninitialised items as VALID.
>
> A recent commit added a call to cache_fresh_locked()
> when an expired item was found.
> The call sets the CACHE_VALID flag, so it is important
> that the item actually is valid.
> There are two ways it could be valid:
> 1/ If ->update has been called to fill in relevant content
> 2/ if CACHE_NEGATIVE is set, to say that content doesn't exist.
>
> An expired item that is waiting for an update will be neither.
> Setting CACHE_VALID will mean that a subsequent call to cache_put()
> will be likely to dereference uninitialised pointers.
>
> So we must make sure the item is valid, and we already have code to do
> that in try_to_negate_entry(). This takes the hash lock and so cannot
> be used directly, so take out the two lines that we need and use them.
>
> Now cache_fresh_locked() is certain to be called only on
> a valid item.
>
> Cc: stable@kernel.org # 2.6.35
> Fixes: 4ecd55ea0742 ("sunrpc: fix cache_head leak due to queued request")
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
> net/sunrpc/cache.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/sunrpc/cache.c b/net/sunrpc/cache.c
> index 12bb23b8e0c5..261131dfa1f1 100644
> --- a/net/sunrpc/cache.c
> +++ b/net/sunrpc/cache.c
> @@ -54,6 +54,7 @@ static void cache_init(struct cache_head *h, struct cache_detail *detail)
> h->last_refresh = now;
> }
>
> +static inline int cache_is_valid(struct cache_head *h);
> static void cache_fresh_locked(struct cache_head *head, time_t expiry,
> struct cache_detail *detail);
> static void cache_fresh_unlocked(struct cache_head *head,
> @@ -105,6 +106,8 @@ static struct cache_head *sunrpc_cache_add_entry(struct cache_detail *detail,
> if (cache_is_expired(detail, tmp)) {
> hlist_del_init_rcu(&tmp->cache_list);
> detail->entries --;
> + if (cache_is_valid(tmp) == -EAGAIN)
> + set_bit(CACHE_NEGATIVE, &tmp->flags);
> cache_fresh_locked(tmp, 0, detail);
> freeme = tmp;
> break;
> --
> 2.14.0.rc0.dirty
>
prev parent reply other threads:[~2019-04-05 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 8:45 [PATCH 0/1] cache_head leak in sunrpc_cache_lookup() Vasily Averin
2018-11-28 23:35 ` J. Bruce Fields
2018-11-29 5:35 ` NeilBrown
2018-12-04 20:42 ` J. Bruce Fields
2019-04-04 22:21 ` NeilBrown
2019-04-05 0:34 ` NeilBrown
2019-04-05 23:52 ` J. Bruce Fields [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=20190405235241.GE8397@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=vvs@virtuozzo.com \
/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