From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Liu Yuntao <liuyuntao10@huawei.com>
Cc: hughd@google.com, akpm@linux-foundation.org,
kirill.shutemov@linux.intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, wuxu.wu@huawei.com,
liusirui@huawei.com, windspectator@gmail.com
Subject: Re: [PATCH] fix judgment error in shmem_is_huge()
Date: Wed, 8 Sep 2021 17:58:44 +0300 [thread overview]
Message-ID: <20210908145844.wqkyfuizqaj5mmrj@box> (raw)
In-Reply-To: <20210908102648.2326917-2-liuyuntao10@huawei.com>
On Wed, Sep 08, 2021 at 06:26:48PM +0800, Liu Yuntao wrote:
> In the case of SHMEM_HUGE_WITHIN_SIZE, the page index is not rounded
> up correctly. When the page index points to the first page in a huge
> page, round_up() cannot bring it to the end of the huge page, but
> to the end of the previous one.
>
> an example:
> HPAGE_PMD_NR on my machine is 512(2 MB huge page size).
> After allcoating a 3000 KB buffer, I access it at location 2050 KB.
> In shmem_is_huge(), the corresponding index happens to be 512.
> After rounded up by HPAGE_PMD_NR, it will still be 512 which is
> smaller than i_size, and shmem_is_huge() will return true.
> As a result, my buffer takes an additional huge page, and that
> shouldn't happen when shmem_enabled is set to within_size.
>
> Fixes: f3f0e1d2150b2b ("khugepaged: add support of collapse for tmpfs/shmem pages")
> Signed-off-by: Liu Yuntao <liuyuntao10@huawei.com>
> ---
> mm/shmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 88742953532c..5747572859d1 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -490,7 +490,7 @@ bool shmem_is_huge(struct vm_area_struct *vma,
> case SHMEM_HUGE_ALWAYS:
> return true;
> case SHMEM_HUGE_WITHIN_SIZE:
> - index = round_up(index, HPAGE_PMD_NR);
> + index = round_up(index + 1, HPAGE_PMD_NR);
> i_size = round_up(i_size_read(inode), PAGE_SIZE);
> if (i_size >= HPAGE_PMD_SIZE && (i_size >> PAGE_SHIFT) >= index)
With the change, the condition can be simplified to
if (i_size >> PAGE_SHIFT >= index)
right?
> return true;
> --
> 2.23.0
>
--
Kirill A. Shutemov
next prev parent reply other threads:[~2021-09-08 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 10:26 [PATCH] virtio-gpu: fix possible memory allocation failure Liu Yuntao
2021-09-08 10:26 ` [PATCH] fix judgment error in shmem_is_huge() Liu Yuntao
2021-09-08 14:58 ` Kirill A. Shutemov [this message]
2021-09-09 2:39 ` Liu Yuntao
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=20210908145844.wqkyfuizqaj5mmrj@box \
--to=kirill@shutemov.name \
--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 \
--cc=liusirui@huawei.com \
--cc=liuyuntao10@huawei.com \
--cc=windspectator@gmail.com \
--cc=wuxu.wu@huawei.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