From: David Hildenbrand <david@redhat.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Andi Kleen <ak@linux.intel.com>,
mhocko@suse.cz, Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH v2 0/6] Fix some bugs about HugeTLB code
Date: Thu, 7 Jan 2021 11:10:21 +0100 [thread overview]
Message-ID: <7971c96c-6b96-2dca-b9d9-d3828b117e66@redhat.com> (raw)
In-Reply-To: <CAMZfGtUcGLZjesq4ztqHXG2PekmJ2q60s3ymjBRmiJ141syK3A@mail.gmail.com>
On 07.01.21 10:40, Muchun Song wrote:
> On Thu, Jan 7, 2021 at 5:30 PM David Hildenbrand <david@redhat.com> wrote:
>>
>> On 06.01.21 09:47, Muchun Song wrote:
>>> This patch series aims to fix some bugs and add some improvements.
>>>
>>> Changelog since v1 -> v2:
>>> - Export set_page_huge_active() in patch #2 to fix.
>>> - Using head[3].mapping to indicate the page is freed in patch #3.
>>> - Flush @free_hpage_work in patch #4.
>>>
>>> Muchun Song (6):
>>> mm: migrate: do not migrate HugeTLB page whose refcount is one
>>> mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page
>>> mm: hugetlb: fix a race between freeing and dissolving the page
>>> mm: hugetlb: add return -EAGAIN for dissolve_free_huge_page
>>> mm: hugetlb: fix a race between isolating and freeing page
>>> mm: hugetlb: remove VM_BUG_ON_PAGE from page_huge_active
>>>
>>> fs/hugetlbfs/inode.c | 3 ++-
>>> include/linux/hugetlb.h | 2 ++
>>> mm/hugetlb.c | 69 +++++++++++++++++++++++++++++++++++++++++++------
>>> mm/migrate.c | 6 +++++
>>> 4 files changed, 71 insertions(+), 9 deletions(-)
>>>
>>
>> Repeating my question regarding ccing stable on selected fixes.
>>
>
> Just add a CC tag in the commit log of the fix patches? Right?
> Sorry, I'm a novice about this. Thanks.
Sure, here is some information:
https://www.kernel.org/doc/html/v4.10/process/stable-kernel-rules.html
Applicable patches should be moved to the beginning of the series.
Add "Cc: stable@vger.kernel.org" similar to "Fixes:" to the respective
patches. In the ideal case, indicate the applicable earliest stable
release where it applies.
E.g., take a look at (random commit)
commit 20b329129009caf1c646152abe09b697227e1c37
Author: Bob Peterson <rpeterso@redhat.com>
Date: Wed Nov 18 08:54:31 2020 -0500
gfs2: Fix regression in freeze_go_sync
...
Fixes: 541656d3a513 ("gfs2: freeze should work on read-only mounts")
Cc: stable@vger.kernel.org # v5.8+
...
Consequently, actually cc when sending out these patches (e.g., let "git
send-email" do it automatically).
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-01-07 10:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 8:47 [PATCH v2 0/6] Fix some bugs about HugeTLB code Muchun Song
2021-01-06 8:47 ` [PATCH v2 1/6] mm: migrate: do not migrate HugeTLB page whose refcount is one Muchun Song
2021-01-06 16:13 ` Michal Hocko
2021-01-07 2:52 ` [External] " Muchun Song
2021-01-07 11:16 ` Michal Hocko
2021-01-07 11:24 ` Muchun Song
2021-01-07 11:48 ` Michal Hocko
2021-01-06 8:47 ` [PATCH v2 2/6] mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page Muchun Song
2021-01-06 16:35 ` Michal Hocko
2021-01-06 19:30 ` Mike Kravetz
2021-01-06 20:02 ` Michal Hocko
2021-01-06 21:07 ` Mike Kravetz
2021-01-07 8:36 ` Michal Hocko
2021-01-07 2:58 ` [External] " Muchun Song
2021-01-06 8:47 ` [PATCH v2 3/6] mm: hugetlb: fix a race between freeing and dissolving the page Muchun Song
2021-01-06 16:56 ` Michal Hocko
2021-01-06 20:58 ` Mike Kravetz
2021-01-07 3:08 ` [External] " Muchun Song
2021-01-07 8:40 ` Michal Hocko
2021-01-08 0:52 ` Mike Kravetz
2021-01-08 8:28 ` Michal Hocko
2021-01-07 5:39 ` [External] " Muchun Song
2021-01-07 8:41 ` Michal Hocko
2021-01-07 8:53 ` Muchun Song
2021-01-07 11:18 ` Michal Hocko
2021-01-07 11:38 ` Muchun Song
2021-01-07 12:38 ` Michal Hocko
2021-01-07 12:59 ` Muchun Song
2021-01-07 14:11 ` Michal Hocko
2021-01-07 15:11 ` Muchun Song
2021-01-08 1:06 ` Mike Kravetz
2021-01-08 2:38 ` Muchun Song
2021-01-08 8:43 ` Michal Hocko
2021-01-08 9:01 ` Muchun Song
2021-01-08 9:31 ` Michal Hocko
2021-01-08 10:08 ` Muchun Song
2021-01-08 11:44 ` Michal Hocko
2021-01-08 11:52 ` Muchun Song
2021-01-08 12:04 ` Michal Hocko
2021-01-08 12:24 ` Muchun Song
2021-01-06 8:47 ` [PATCH v2 4/6] mm: hugetlb: add return -EAGAIN for dissolve_free_huge_page Muchun Song
2021-01-06 17:07 ` Michal Hocko
2021-01-07 3:11 ` [External] " Muchun Song
2021-01-07 8:39 ` Michal Hocko
2021-01-07 9:01 ` Muchun Song
2021-01-07 11:22 ` Michal Hocko
2021-01-06 8:47 ` [PATCH v2 5/6] mm: hugetlb: fix a race between isolating and freeing page Muchun Song
2021-01-06 17:10 ` Michal Hocko
2021-01-06 8:47 ` [PATCH v2 6/6] mm: hugetlb: remove VM_BUG_ON_PAGE from page_huge_active Muchun Song
2021-01-06 17:16 ` Michal Hocko
2021-01-08 22:24 ` Mike Kravetz
2021-01-09 4:07 ` [External] " Muchun Song
2021-01-07 9:30 ` [PATCH v2 0/6] Fix some bugs about HugeTLB code David Hildenbrand
2021-01-07 9:40 ` [External] " Muchun Song
2021-01-07 10:10 ` David Hildenbrand [this message]
2021-01-07 10:16 ` 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=7971c96c-6b96-2dca-b9d9-d3828b117e66@redhat.com \
--to=david@redhat.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=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=songmuchun@bytedance.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).