[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220517163907.223f16f071b57b9e3d062ff8@linux-foundation.org>
Date: Tue, 17 May 2022 16:39:07 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Miaohe Lin <linmiaohe@...wei.com>
Cc: David Hildenbrand <david@...hat.com>, <willy@...radead.org>,
<vbabka@...e.cz>, <dhowells@...hat.com>, <neilb@...e.de>,
<apopple@...dia.com>, <surenb@...gle.com>, <peterx@...hat.com>,
<naoya.horiguchi@....com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 06/15] mm/swap: remove buggy cache->nr check in
refill_swap_slots_cache
On Mon, 16 May 2022 10:00:43 +0800 Miaohe Lin <linmiaohe@...wei.com> wrote:
> On 2022/5/12 21:37, David Hildenbrand wrote:
> > On 09.05.22 15:14, Miaohe Lin wrote:
> >> refill_swap_slots_cache is always called when cache->nr is 0. And if
> >> cache->nr != 0, we should return cache->nr instead of 0. So remove
> >> such buggy and confusing check.
> >
> > Not sure about the "cache->nr != 0, we should return cache->nr instead
> > of 0" part, I'd just drop that from the patch description. We'd actually
> > end up overwriting cache->nr after your change, which doesn't sound
> > right and also different to what you describe here.
>
> Will do.
I've updated the changleog to simply
: refill_swap_slots_cache is always called when cache->nr is 0. So remove
: such buggy and confusing check.
Powered by blists - more mailing lists