[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e5d67774-a006-e533-d928-64a4407cbb16@virtuozzo.com>
Date: Sun, 5 Aug 2018 08:30:43 +0300
From: Kirill Tkhai <ktkhai@...tuozzo.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, vdavydov.dev@...il.com,
mhocko@...e.com, aryabinin@...tuozzo.com, ying.huang@...el.com,
penguin-kernel@...ove.SAKURA.ne.jp, shakeelb@...gle.com,
jbacik@...com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Use special value SHRINKER_REGISTERING instead
list_empty() check
On 05.08.2018 03:03, Matthew Wilcox wrote:
> On Sat, Aug 04, 2018 at 09:42:05PM +0300, Kirill Tkhai wrote:
>> This is exactly the thing the patch makes. Instead of inserting a shrinker pointer
>> to idr, it inserts a fake value SHRINKER_REGISTERING there. The patch makes impossible
>> to dereference a shrinker unless it's completely registered.
>
> - id = idr_alloc(&shrinker_idr, shrinker, 0, 0, GFP_KERNEL);
> + id = idr_alloc(&shrinker_idr, SHRINKER_REGISTERING, 0, 0, GFP_KERNEL);
>
> Instead:
>
> + id = idr_alloc(&shrinker_idr, NULL, 0, 0, GFP_KERNEL);
>
> ... and the rest of your patch becomes even simpler.
The patch, we are discussing at the moment, does *exactly* this:
https://lkml.org/lkml/2018/8/3/588
It looks like you missed this hunk in the patch.
Powered by blists - more mailing lists