From: Greg KH <gregkh@linuxfoundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: chrisl@kernel.org, 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>,
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 v2 0/3] Yu Zhao's memory fix backport
Date: Mon, 21 Oct 2024 11:47:06 +0200 [thread overview]
Message-ID: <2024102139-hangnail-thimble-38d4@gregkh> (raw)
In-Reply-To: <3d7865c0-f269-413f-bb9d-54f46acbe489@suse.cz>
On Fri, Oct 18, 2024 at 11:59:50PM +0200, Vlastimil Babka wrote:
> On 10/18/24 7:27 PM, chrisl@kernel.org wrote:
> > A few commits from Yu Zhao have been merged into 6.12.
> > They need to be backported to 6.11.
>
> But aside from adding the s-o-b, you still didn't say why?
>
> > - c2a967f6ab0ec ("mm/hugetlb_vmemmap: don't synchronize_rcu() without HVO")
>
> Especially for this one.
>
> > - 95599ef684d01 ("mm/codetag: fix pgalloc_tag_split()")
> > - e0a955bf7f61c ("mm/codetag: add pgalloc_tag_copy()")
>
> And those are marked already, but actually Kent wanted to hold off in
> response to your v1, due to suspecting them to cause problems?
Ok, I'm going to drop these from my review queue for now. Please, when
you all work it out, resend if they are still deemed necessary for
6.11.y or any other stable tree.
thanks,
greg k-h
prev parent reply other threads:[~2024-10-21 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 17:27 [PATCH 6.11.y v2 0/3] Yu Zhao's memory fix backport chrisl
2024-10-18 17:27 ` [PATCH 6.11.y v2 1/3] mm/hugetlb_vmemmap: don't synchronize_rcu() without HVO chrisl
2024-10-18 17:27 ` [PATCH 6.11.y v2 2/3] mm/codetag: fix pgalloc_tag_split() chrisl
2024-10-18 17:27 ` [PATCH 6.11.y v2 3/3] mm/codetag: add pgalloc_tag_copy() chrisl
2024-10-18 21:59 ` [PATCH 6.11.y v2 0/3] Yu Zhao's memory fix backport Vlastimil Babka
2024-10-21 9:47 ` Greg KH [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=2024102139-hangnail-thimble-38d4@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