[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190326133603.GB16837@redhat.com>
Date: Tue, 26 Mar 2019 14:36:04 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Christopher Lameter <cl@...ux.com>
Cc: Matthew Wilcox <willy@...radead.org>,
Waiman Long <longman@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
selinux@...r.kernel.org, Paul Moore <paul@...l-moore.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Eric Paris <eparis@...isplace.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>
Subject: Re: [PATCH 2/4] signal: Make flush_sigqueue() use free_q to release
memory
On 03/25, Christopher Lameter wrote:
>
> On Fri, 22 Mar 2019, Matthew Wilcox wrote:
>
> > Only for SLAB and SLUB. SLOB requires that you pass a pointer to the
> > slab cache; it has no way to look up the slab cache from the object.
>
> Well then we could either fix SLOB to conform to the others or add a
> kmem_cache_free_rcu() variant.
Speaking of struct sigqueue we can simply use call_rcu() but see my previous
email, I am not sure this is the best option.
Oleg.
Powered by blists - more mailing lists