From: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
To: David Rientjes <rientjes@google.com>
Cc: "cl@linux.com" <cl@linux.com>,
"penberg@kernel.org" <penberg@kernel.org>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 回复: [PATCH] mm/slab.c: add node spinlock protect in __cache_free_alien
Date: Wed, 29 Jul 2020 01:25:40 +0000 [thread overview]
Message-ID: <BYAPR11MB2632BEC45DC867E80F841B82FF700@BYAPR11MB2632.namprd11.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2007281238580.2664959@chino.kir.corp.google.com>
________________________________________
发件人: David Rientjes <rientjes@google.com>
发送时间: 2020年7月29日 3:46
收件人: Zhang, Qiang
抄送: cl@linux.com; penberg@kernel.org; iamjoonsoo.kim@lge.com; akpm@linux-foundation.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org
主题: Re: [PATCH] mm/slab.c: add node spinlock protect in __cache_free_alien
On Tue, 28 Jul 2020, qiang.zhang@windriver.com wrote:
> From: Zhang Qiang <qiang.zhang@windriver.com>
>
> We should add node spinlock protect "n->alien" which may be
> assigned to NULL in cpuup_canceled func. cause address access
> exception.
>
>Hi, do you have an example NULL pointer dereference where you have hit
>this?
>This rather looks like something to fix up in cpuup_canceled() since it's
>currently manipulating the alien cache for the canceled cpu's node.
yes , it is fix up in cpuup_canceled it's
currently manipulating the alien cache for the canceled cpu's node which may be the same as the node being operated on in the __cache_free_alien func.
void cpuup_canceled
{
n = get_node(cachep, node);
spin_lock_irq(&n->list_lock);
...
n->alien = NULL;
spin_unlock_irq(&n->list_lock);
....
}
> Fixes: 18bf854117c6 ("slab: use get_node() and kmem_cache_node() functions")
> Signed-off-by: Zhang Qiang <qiang.zhang@windriver.com>
> ---
> mm/slab.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index a89633603b2d..290523c90b4e 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -759,8 +759,10 @@ static int __cache_free_alien(struct kmem_cache *cachep, void *objp,
>
> n = get_node(cachep, node);
> STATS_INC_NODEFREES(cachep);
> + spin_lock(&n->list_lock);
> if (n->alien && n->alien[page_node]) {
> alien = n->alien[page_node];
> + spin_unlock(&n->list_lock);
> ac = &alien->ac;
> spin_lock(&alien->lock);
> if (unlikely(ac->avail == ac->limit)) {
> @@ -769,14 +771,15 @@ static int __cache_free_alien(struct kmem_cache *cachep, void *objp,
> }
> ac->entry[ac->avail++] = objp;
> spin_unlock(&alien->lock);
> - slabs_destroy(cachep, &list);
> } else {
> + spin_unlock(&n->list_lock);
> n = get_node(cachep, page_node);
> spin_lock(&n->list_lock);
> free_block(cachep, &objp, 1, page_node, &list);
> spin_unlock(&n->list_lock);
> - slabs_destroy(cachep, &list);
> }
> +
> + slabs_destroy(cachep, &list);
> return 1;
> }
>
> --
> 2.26.2
>
>
next prev parent reply other threads:[~2020-07-29 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:55 [PATCH] mm/slab.c: add node spinlock protect in __cache_free_alien qiang.zhang
2020-07-28 19:46 ` David Rientjes
2020-07-29 1:25 ` Zhang, Qiang [this message]
2020-07-29 23:32 ` 回复: " David Rientjes
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=BYAPR11MB2632BEC45DC867E80F841B82FF700@BYAPR11MB2632.namprd11.prod.outlook.com \
--to=qiang.zhang@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).