[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f06e4a39-39e7-44de-dbc8-dc82ead37047@redhat.com>
Date: Fri, 29 Apr 2022 12:08:56 +0200
From: David Hildenbrand <david@...hat.com>
To: Miaohe Lin <linmiaohe@...wei.com>, akpm@...ux-foundation.org,
mike.kravetz@...cle.com, naoya.horiguchi@....com
Cc: ying.huang@...el.com, hch@....de, dhowells@...hat.com,
cl@...ux.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/4] mm/migration: return errno when isolate_huge_page
failed
On 25.04.22 15:27, Miaohe Lin wrote:
> We might fail to isolate huge page due to e.g. the page is under migration
> which cleared HPageMigratable. So we should return -EBUSY in this case
> rather than always return 1 which could confuse the user. Also we make
> the prototype of isolate_huge_page consistent with isolate_lru_page to
> improve the readability.
>
> Fixes: e8db67eb0ded ("mm: migrate: move_pages() supports thp migration")
If this is a fix, what's the runtime effect of it?
You state "could confuse", which doesn't indicate an actual BUG to me.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists