[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0a04e9953b0e714ec906fbee38f36b08e58da8a.camel@gmx.de>
Date: Wed, 06 Nov 2019 12:26:24 +0100
From: Robert Stupp <snazy@....de>
To: Johannes Weiner <hannes@...xchg.org>,
Vlastimil Babka <vbabka@...e.cz>
Cc: Michal Hocko <mhocko@...nel.org>,
Josef Bacik <josef@...icpanda.com>, Jan Kara <jack@...e.cz>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org, Linux MM <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Potyra, Stefan" <Stefan.Potyra@...ktrobit.com>
Subject: Re: mlockall(MCL_CURRENT) blocking infinitely
Maybe a native and wrong idea, but would it work to call
__get_user_pages_locked() instead of __get_user_pages() in
populate_vma_page_range() ?
On Wed, 2019-11-06 at 11:25 +0100, Robert Stupp wrote:
> Here's one more dmesg output with more information captured in
> __get_user_pages() as well. It basically confirms that
> handle_mm_fault() returns VM_FAULT_RETRY.
>
> I'm not sure where and what to change ("fix with a FOLL_TRIED
> somewhere") to make it work. My (uneducated) impression is, that only
> __get_user_pages() needs to be changed - but I might be wrong.
>
Powered by blists - more mailing lists