From: Song Liu <songliubraving@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: open list <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"matthew.wilcox@oracle.com" <matthew.wilcox@oracle.com>,
Kernel Team <Kernel-team@fb.com>,
"william.kucharski@oracle.com" <william.kucharski@oracle.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v5 1/2] mm,thp: recheck each page before collapsing file THP
Date: Fri, 8 Nov 2019 03:58:44 +0000 [thread overview]
Message-ID: <47A1A0C0-8E38-4F4E-B7D6-7B390E7F7813@fb.com> (raw)
In-Reply-To: <20191107195328.600f302bbde69cf9c1089500@linux-foundation.org>
> On Nov 7, 2019, at 7:53 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 5 Nov 2019 22:09:29 -0800 Song Liu <songliubraving@fb.com> wrote:
>
>> In collapse_file(), for !is_shmem case, current check cannot guarantee
>> the locked page is up-to-date. Specifically, xas_unlock_irq() should
>> not be called before lock_page() and get_page(); and it is necessary to
>> recheck PageUptodate() after locking the page.
>>
>> With this bug and CONFIG_READ_ONLY_THP_FOR_FS=y, madvise(HUGE)'ed .text
>> may contain corrupted data. This is because khugepaged mistakenly
>> collapses some not up-to-date sub pages into a huge page, and assumes
>> the huge page is up-to-date. This will NOT corrupt data in the disk,
>> because the page is read-only and never written back. Fix this by
>> properly checking PageUptodate() after locking the page. This check
>> replaces "VM_BUG_ON_PAGE(!PageUptodate(page), page);".
>>
>> Also, move PageDirty() check after locking the page. Current
>> khugepaged should not try to collapse dirty file THP, because it is
>> limited to read-only .text. The only case we hit a dirty page here is
>> when the page hasn't been written since write. Bail out and retry when
>> this happens.
>
> Incorrect data is pretty serious. Should we backport this into -stable
> kernels?
>
> (I suspect I already asked this in response to earier versions, sorry ;))
This is new feature (and new bug :( ) in 5.4. So no need to back port.
Thanks,
Song
next prev parent reply other threads:[~2019-11-08 3:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 6:09 [PATCH v5 0/2] fix and improvement for file THP Song Liu
2019-11-06 6:09 ` [PATCH v5 1/2] mm,thp: recheck each page before collapsing " Song Liu
2019-11-08 3:53 ` Andrew Morton
2019-11-08 3:58 ` Song Liu [this message]
2019-11-13 23:47 ` Song Liu
2019-11-15 0:10 ` Andrew Morton
2019-11-06 6:09 ` [PATCH v5 2/2] mm/thp: flush file for !is_shmem PageDirty() case in collapse_file() Song Liu
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=47A1A0C0-8E38-4F4E-B7D6-7B390E7F7813@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.wilcox@oracle.com \
--cc=william.kucharski@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).