[Top] [All Lists]

Re: [PATCH] mm: fix direct reclaim writeback regression

To: Hugh Dickins <hughd@xxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] mm: fix direct reclaim writeback regression
From: Vlastimil Babka <vbabka@xxxxxxx>
Date: Sun, 27 Jul 2014 00:45:20 +0200
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, David Rientjes <rientjes@xxxxxxxxxx>, Rik van Riel <riel@xxxxxxxxxx>, Johannes Weiner <hannes@xxxxxxxxxxx>, Dave Jones <davej@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <alpine.LSU.2.11.1407261248140.13796@xxxxxxxxxxxx>
References: <alpine.LSU.2.11.1407261248140.13796@xxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
On 07/26/2014 09:58 PM, Hugh Dickins wrote:
> Yes, 3.16-rc1's 68711a746345 ("mm, migration: add destination page
> freeing callback") has provided such a way to compaction: if migrating
> a SwapBacked page fails, its newpage may be put back on the list for
> later use with PageSwapBacked still set, and nothing will clear it.

Ugh good catch. So is this the only flag that can become "stray" like
this? It seems so from quick check...

> Whether that can do anything worse than issue WARN_ON_ONCEs, and get
> some statistics wrong, is unclear: easier to fix than to think through
> the consequences.
> Fixing it here, before the put_new_page(), addresses the bug directly,
> but is probably the worst place to fix it.  Page migration is doing too
> many parts of the job on too many levels: fixing it in move_to_new_page()
> to complement its SetPageSwapBacked would be preferable, except why is it
> (and newpage->mapping and newpage->index) done there, rather than down in
> migrate_page_move_mapping(), once we are sure of success?  Not a cleanup
> to get into right now, especially not with memcg cleanups coming in 3.17.
> Reported-by: Dave Jones <davej@xxxxxxxxxx>
> Signed-off-by: Hugh Dickins <hughd@xxxxxxxxxx>
> ---
>  mm/migrate.c |    5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> --- 3.16-rc6/mm/migrate.c     2014-06-29 15:22:10.584003935 -0700
> +++ linux/mm/migrate.c        2014-07-26 11:28:34.488126591 -0700
> @@ -988,9 +988,10 @@ out:
>        * it.  Otherwise, putback_lru_page() will drop the reference grabbed
>        * during isolation.
>        */
> -     if (rc != MIGRATEPAGE_SUCCESS && put_new_page)
> +     if (rc != MIGRATEPAGE_SUCCESS && put_new_page) {
> +             ClearPageSwapBacked(newpage);
>               put_new_page(newpage, private);
> -     else
> +     } else
>               putback_lru_page(newpage);
>       if (result) {

What about unmap_and_move_huge_page()? Seems to me it can also get the
same stray flag. Although compaction, who is the only user so far of
custom put_new_page, wouldn't of course migrate huge pages. But might
bite us in the future, if a new user appears before a cleanup...


<Prev in Thread] Current Thread [Next in Thread>