From: Song Liu <songliubraving@fb.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm,thp: stop leaking unreleased file pages
Date: Mon, 25 May 2020 00:05:40 +0000 [thread overview]
Message-ID: <649C7E6B-BD4B-49F6-8CF2-E600AB4B94FF@fb.com> (raw)
In-Reply-To: <alpine.LSU.2.11.2005231837500.1766@eggly.anvils>
> On May 23, 2020, at 6:50 PM, Hugh Dickins <hughd@google.com> wrote:
>
> When collapse_file() calls try_to_release_page(), it has already
> isolated the page: so if releasing buffers happens to fail (as it
> sometimes does), remember to putback_lru_page(): otherwise that page is
> left unreclaimable and unfreeable, and the file extent uncollapsible.
>
> Signed-off-by: Hugh Dickins <hughd@google.com>
> Fixes: 99cb0dbd47a1 ("mm,thp: add read-only THP support for (non-shmem) FS")
> Cc: stable@vger.kernel.org # v5.4+
Acked-by: Song Liu <songliubraving@fb.com>
Thanks for the fix!
> ---
>
> mm/khugepaged.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- 5.7-rc6/mm/khugepaged.c 2020-04-12 16:24:37.710999073 -0700
> +++ linux/mm/khugepaged.c 2020-05-10 17:06:21.788398646 -0700
> @@ -1692,6 +1692,7 @@ static void collapse_file(struct mm_stru
> if (page_has_private(page) &&
> !try_to_release_page(page, GFP_KERNEL)) {
> result = SCAN_PAGE_HAS_PRIVATE;
> + putback_lru_page(page);
> goto out_unlock;
> }
>
next prev parent reply other threads:[~2020-05-25 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 1:50 Hugh Dickins
2020-05-25 0:05 ` Song Liu [this message]
2020-05-25 4:32 ` Kirill A. Shutemov
2020-05-26 16:01 ` Johannes Weiner
2020-05-27 21:28 ` Hugh Dickins
2020-05-28 8:51 ` Naresh Kamboju
2020-06-03 21:51 ` Matthew Wilcox
2020-06-03 22:19 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=649C7E6B-BD4B-49F6-8CF2-E600AB4B94FF@fb.com \
--to=songliubraving@fb.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox