From: Song Liu <songliubraving@fb.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Hugh Dickins <hughd@google.com>,
"sunhao.th@gmail.com" <sunhao.th@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"andrea.righi@canonical.com" <andrea.righi@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mm: khugepaged: skip huge page collapse for special files
Date: Wed, 27 Oct 2021 20:34:49 +0000 [thread overview]
Message-ID: <C8C6E50C-D300-40D4-AA5C-490F673BADFE@fb.com> (raw)
In-Reply-To: <20211027195221.3825-1-shy828301@gmail.com>
> On Oct 27, 2021, at 12:52 PM, Yang Shi <shy828301@gmail.com> wrote:
>
> The read-only THP for filesystems would collapse THP for file opened
> readonly and mapped with VM_EXEC, the intended usecase is to avoid TLB
> miss for large text segment. But it doesn't restrict the file types so
> THP could be collapsed for non-regular file, for example, block device,
> if it is opened readonly and mapped with EXEC permission. This may
> cause bugs, like [1] and [2].
>
> This is definitely not intended usecase, so just collapsing THP for regular
> file in order to close the attack surface.
>
> [1] https://lore.kernel.org/lkml/CACkBjsYwLYLRmX8GpsDpMthagWOjWWrNxqY6ZLNQVr6yx+f5vA@mail.gmail.com/
> [2] https://lore.kernel.org/linux-mm/000000000000c6a82505ce284e4c@google.com/
>
> Fixes: 99cb0dbd47a1 ("mm,thp: add read-only THP support for (non-shmem) FS")
> Reported-by: Hao Sun <sunhao.th@gmail.com>
> Reported-by: syzbot+aae069be1de40fb11825@syzkaller.appspotmail.com
> Cc: Hao Sun <sunhao.th@gmail.com>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Song Liu <songliubraving@fb.com>
> Cc: Andrea Righi <andrea.righi@canonical.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Hugh Dickins <hughd@google.com>
> Signed-off-by: Yang Shi <shy828301@gmail.com>
> ---
> The patch is basically based off the proposal from Hugh
> (https://lore.kernel.org/linux-mm/a07564a3-b2fc-9ffe-3ace-3f276075ea5c@google.com/).
> It seems Hugh is too busy to prepare the patch for formal submission (I
> didn't hear from him by pinging him a couple of times on mailing list),
> so I prepared the patch and added his SOB.
>
> mm/khugepaged.c | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 045cc579f724..e91b7271275e 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -445,22 +445,25 @@ static bool hugepage_vma_check(struct vm_area_struct *vma,
> if (!transhuge_vma_enabled(vma, vm_flags))
> return false;
>
> - /* Enabled via shmem mount options or sysfs settings. */
> - if (shmem_file(vma->vm_file) && shmem_huge_enabled(vma)) {
> + if (vma->vm_file)
> return IS_ALIGNED((vma->vm_start >> PAGE_SHIFT) - vma->vm_pgoff,
> HPAGE_PMD_NR);
Am I misreading this? If we return here for vma->vm_file, the following
logic (shmem_file(), etc.) would be skipped, no?
Thanks,
Song
> - }
> +
> + /* Enabled via shmem mount options or sysfs settings. */
> + if (shmem_file(vma->vm_file))
> + return shmem_huge_enabled(vma);
>
> /* THP settings require madvise. */
> if (!(vm_flags & VM_HUGEPAGE) && !khugepaged_always())
> return false;
>
> - /* Read-only file mappings need to be aligned for THP to work. */
> + /* Only regular file is valid */
> if (IS_ENABLED(CONFIG_READ_ONLY_THP_FOR_FS) && vma->vm_file &&
> - !inode_is_open_for_write(vma->vm_file->f_inode) &&
> (vm_flags & VM_EXEC)) {
> - return IS_ALIGNED((vma->vm_start >> PAGE_SHIFT) - vma->vm_pgoff,
> - HPAGE_PMD_NR);
> + struct inode *inode = vma->vm_file->f_inode;
> +
> + return !inode_is_open_for_write(inode) &&
> + S_ISREG(inode->i_mode);
> }
>
> if (!vma->anon_vma || vma->vm_ops)
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-10-27 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 19:52 Yang Shi
2021-10-27 20:34 ` Song Liu [this message]
2021-10-27 20:44 ` Yang Shi
2021-10-27 20:53 ` Andrew Morton
2021-10-27 21:57 ` Yang Shi
2021-10-27 20:50 ` Matthew Wilcox
2021-10-27 21:32 ` Yang Shi
2021-10-27 21:37 ` Matthew Wilcox
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=C8C6E50C-D300-40D4-AA5C-490F673BADFE@fb.com \
--to=songliubraving@fb.com \
--cc=akpm@linux-foundation.org \
--cc=andrea.righi@canonical.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=sunhao.th@gmail.com \
--cc=willy@infradead.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