linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: Muchun Song <songmuchun@bytedance.com>, akpm@linux-foundation.org
Cc: n-horiguchi@ah.jp.nec.com, ak@linux.intel.com, mhocko@suse.cz,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 2/6] mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page
Date: Mon, 11 Jan 2021 15:04:43 -0800	[thread overview]
Message-ID: <3ee2bcf5-35cf-1062-433d-56b4c7f011a0@oracle.com> (raw)
In-Reply-To: <20210110124017.86750-3-songmuchun@bytedance.com>

On 1/10/21 4:40 AM, Muchun Song wrote:
> If a new hugetlb page is allocated during fallocate it will not be
> marked as active (set_page_huge_active) which will result in a later
> isolate_huge_page failure when the page migration code would like to
> move that page. Such a failure would be unexpected and wrong.
> 
> Only export set_page_huge_active, just leave clear_page_huge_active
> as static. Because there are no external users.
> 
> Fixes: 70c3547e36f5 (hugetlbfs: add hugetlbfs_fallocate())
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> Cc: stable@vger.kernel.org
> ---
>  fs/hugetlbfs/inode.c    | 3 ++-
>  include/linux/hugetlb.h | 2 ++
>  mm/hugetlb.c            | 2 +-
>  3 files changed, 5 insertions(+), 2 deletions(-)

Thanks.

Although page_huge_active is declared in page-flags.h, I much prefer the
declaration of set_page_huge_active to be in hugetlb.c.

Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
-- 
Mike Kravetz


  reply	other threads:[~2021-01-11 23:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 12:40 [PATCH v3 0/6] Fix some bugs about HugeTLB code Muchun Song
2021-01-10 12:40 ` [PATCH v3 1/6] mm: migrate: do not migrate HugeTLB page whose refcount is one Muchun Song
2021-01-12  9:42   ` Michal Hocko
2021-01-12  9:43     ` [External] " Muchun Song
2021-01-12 11:00   ` David Hildenbrand
2021-01-12 11:11     ` David Hildenbrand
2021-01-12 11:27       ` Michal Hocko
2021-01-12 11:34         ` David Hildenbrand
2021-01-12 12:16           ` Michal Hocko
2021-01-12 14:23             ` Michal Hocko
2021-01-12 14:41               ` David Hildenbrand
2021-01-12 14:53                 ` Michal Hocko
2021-01-12 20:12                   ` Mike Kravetz
2021-01-12 13:40       ` [External] " Muchun Song
2021-01-12 13:51         ` David Hildenbrand
2021-01-12 14:17           ` Muchun Song
2021-01-12 14:28             ` David Hildenbrand
2021-01-12 14:59               ` Muchun Song
2021-01-10 12:40 ` [PATCH v3 2/6] mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page Muchun Song
2021-01-11 23:04   ` Mike Kravetz [this message]
2021-01-12  9:45   ` Michal Hocko
2021-01-10 12:40 ` [PATCH v3 3/6] mm: hugetlb: fix a race between freeing and dissolving the page Muchun Song
2021-01-12  1:06   ` Mike Kravetz
2021-01-12 10:02   ` Michal Hocko
2021-01-12 10:13     ` [External] " Muchun Song
2021-01-12 11:17       ` Michal Hocko
2021-01-12 11:43         ` Muchun Song
2021-01-12 12:37           ` Michal Hocko
2021-01-12 15:05             ` Muchun Song
2021-01-10 12:40 ` [PATCH v3 4/6] mm: hugetlb: add return -EAGAIN for dissolve_free_huge_page Muchun Song
2021-01-12  1:20   ` Mike Kravetz
2021-01-12  8:33     ` Michal Hocko
2021-01-12  9:51       ` [External] " Muchun Song
2021-01-12 10:06         ` Michal Hocko
2021-01-12 10:49           ` Muchun Song
2021-01-12 11:11             ` Michal Hocko
2021-01-12 11:34               ` Muchun Song
2021-01-10 12:40 ` [PATCH v3 5/6] mm: hugetlb: fix a race between isolating and freeing page Muchun Song
2021-01-10 12:40 ` [PATCH v3 6/6] mm: hugetlb: remove VM_BUG_ON_PAGE from page_huge_active Muchun Song

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=3ee2bcf5-35cf-1062-433d-56b4c7f011a0@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=songmuchun@bytedance.com \
    --cc=stable@vger.kernel.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