linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, songmuchun@bytedance.com,
	mike.kravetz@oracle.com, willy@infradead.org,
	tsahu@linux.ibm.com, jhubbard@nvidia.com
Subject: Re: [PATCH mm-stable] mm/hugetlb: set head flag before setting compound_order in __prep_compound_gigantic_folio
Date: Tue, 13 Dec 2022 09:42:27 +0100	[thread overview]
Message-ID: <87b0dd5c-f746-b60e-caf5-375ac342c7bd@redhat.com> (raw)
In-Reply-To: <20221212225529.22493-1-sidhartha.kumar@oracle.com>

On 12.12.22 23:55, Sidhartha Kumar wrote:
> folio_set_compound_order() checks if the passed in folio is a large folio.
> A large folio is indicated by the PG_head flag. Call __folio_set_head()
> before setting the order.
> 
> Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
> Reported-by: David Hildenbrand <david@redhat.com>
> ---
> Hi David,
> I tested this by doing:
> 
> echo 10 > /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages
> echo 0 > /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages

Thanks, that should be good enough.

> 
> and checking dmesg. Let me know if there are other ways of testing
> you would like to see run.
> 
> Hi Andrew,
> This can be folded into d1c6095572d0cf00c0cd30378639ff9387b34edd
> mm/hugetlb: convert hugetlb prep functions to folios.
> 
> However, there is still ongoing discussion with this patch series,
> specifically with patch 1 9fd330582b2f mm: add folio dtor and order setter
> functions, so I'm not sure if this series should be a part of the 6.2 merge
> window. I am planning to send a v6 within the next few days to implement
> the suggested changes.

Whatever is in mm-stable is supposed to go upstream as-is and even the
commit ids will remain stable, meaning we an only queue fixes on top.

Therefore, mm-stable now contains:

commit c45bc55a99957b20e4e0333bcd42e12d1833a7f5 (mm/mm-stable)
Author: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Date:   Mon Dec 12 14:55:29 2022 -0800

     mm/hugetlb: set head flag before setting compound_order in __prep_compound_gigantic_folio
     
     folio_set_compound_order() checks if the passed in folio is a large folio.
     A large folio is indicated by the PG_head flag.  Call __folio_set_head()
     before setting the order.
     
     Link: https://lkml.kernel.org/r/20221212225529.22493-1-sidhartha.kumar@oracle.com
     Fixes: d1c6095572d0 ("mm/hugetlb: convert hugetlb prep functions to folios")
     Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
     Reported-by: David Hildenbrand <david@redhat.com>
     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>


So, best send any future changes against mm-stable instead of sending out a v6.

-- 
Thanks,

David / dhildenb



      reply	other threads:[~2022-12-13  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 22:55 Sidhartha Kumar
2022-12-13  8:42 ` David Hildenbrand [this message]

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=87b0dd5c-f746-b60e-caf5-375ac342c7bd@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=sidhartha.kumar@oracle.com \
    --cc=songmuchun@bytedance.com \
    --cc=tsahu@linux.ibm.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