From: Greg KH <gregkh@linuxfoundation.org>
To: chrisl@kernel.org
Cc: stable@vger.kernel.org, Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Yu Zhao <yuzhao@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Vlastimil Babka <vbabka@suse.cz>,
kernel test robot <oliver.sang@intel.com>,
Janosch Frank <frankja@linux.ibm.com>,
Marc Hartmayer <mhartmay@linux.ibm.com>
Subject: Re: [PATCH 6.11.y 0/3] : Yu Zhao's memory fix backport
Date: Fri, 18 Oct 2024 07:58:41 +0200 [thread overview]
Message-ID: <2024101856-avoid-unsorted-fc33@gregkh> (raw)
In-Reply-To: <20241017-stable-yuzhao-v1-0-3a4566660d44@kernel.org>
On Thu, Oct 17, 2024 at 02:58:01PM -0700, chrisl@kernel.org wrote:
> A few commits from Yu Zhao have been merged into 6.12.
> They need to be backported to 6.11.
Why?
> - c2a967f6ab0ec ("mm/hugetlb_vmemmap: don't synchronize_rcu() without HVO")
> - 95599ef684d01 ("mm/codetag: fix pgalloc_tag_split()")
> - e0a955bf7f61c ("mm/codetag: add pgalloc_tag_copy()")
For mm changes, we need an explicit ack from the mm maintainers to take
patches into the stable tree. Why were these not tagged with the normal
"cc: stable@" tag in the first place?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-18 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 21:58 [PATCH 6.11.y 0/3] : Yu Zhao's memory fix backport chrisl
2024-10-17 21:58 ` [PATCH 6.11.y 1/3] mm/hugetlb_vmemmap: don't synchronize_rcu() without HVO chrisl
2024-10-17 21:58 ` [PATCH 6.11.y 2/3] mm/codetag: fix pgalloc_tag_split() chrisl
2024-10-18 8:29 ` Greg KH
2024-10-18 17:15 ` Chris Li
2024-10-17 21:58 ` [PATCH 6.11.y 3/3] mm/codetag: add pgalloc_tag_copy() chrisl
2024-10-18 5:58 ` Greg KH [this message]
2024-10-18 6:39 ` [PATCH 6.11.y 0/3] : Yu Zhao's memory fix backport Kent Overstreet
2024-10-18 8:18 ` Vlastimil Babka
2024-10-18 8:30 ` Greg KH
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=2024101856-avoid-unsorted-fc33@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=kent.overstreet@linux.dev \
--cc=mhartmay@linux.ibm.com \
--cc=muchun.song@linux.dev \
--cc=oliver.sang@intel.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=yuzhao@google.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