linux-kernel - Re: [PATCH v2 1/1] mm/vmscan.c: Prevent allocating shrinker

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20211207175338.229c52144a67fc1a76b5840c@linux-foundation.org>
Date:   Tue, 7 Dec 2021 17:53:38 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Nico Pache <npache@...hat.com>
Cc:     Matthew Wilcox <willy@...radead.org>, mhocko@...e.com,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        shakeelb@...gle.com, ktkhai@...tuozzo.com, shy828301@...il.com,
        guro@...com, vbabka@...e.cz, vdavydov.dev@...il.com,
        raquini@...hat.com, david@...hat.com
Subject: Re: [PATCH v2 1/1] mm/vmscan.c: Prevent allocating shrinker_info on
 offlined nodes

On Tue, 7 Dec 2021 19:25:25 -0500 Nico Pache <npache@...hat.com> wrote:

> 
> 
> On 12/7/21 18:34, Matthew Wilcox wrote:
> > On Tue, Dec 07, 2021 at 05:40:13PM -0500, Nico Pache wrote:
> >> +++ b/mm/vmscan.c
> >> @@ -222,13 +222,16 @@ static int expand_one_shrinker_info(struct mem_cgroup *memcg,
> >>  	int size = map_size + defer_size;
> >>  
> >>  	for_each_node(nid) {
> >> +		int tmp = nid;
> >>  		pn = memcg->nodeinfo[nid];
> >>  		old = shrinker_info_protected(memcg, nid);
> >>  		/* Not yet online memcg */
> >>  		if (!old)
> >>  			return 0;
> >>  
> >> -		new = kvmalloc_node(sizeof(*new) + size, GFP_KERNEL, nid);
> >> +		if(!node_online(nid))
> >> +			tmp = numa_mem_id();
> >> +		new = kvmalloc_node(sizeof(*new) + size, GFP_KERNEL, tmp);
> >>  		if (!new)
> > 
> > Why should this be fixed here and not in, say, kvmalloc_node()?
> 
> according to Michal, the caller should be responsible for making sure it is
> allocating on a correct node. This avoids adding branches to hot-paths and
> wasting cycles. Im not opposed to moving it to kvmalloc_node, but it may result
> in masking other issues from other callers.
> > 

Yes, kvmalloc_node(nid) should allocate on `nid', or should fail.

A new kvmalloc_try_node() or whatever would express this idea.