From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Hugh Dickins <hughd@google.com>, Linux MM <linux-mm@kvack.org>,
Matthew Auld <matthew.auld@intel.com>,
"Intel-gfx@lists.freedesktop.org"
<Intel-gfx@lists.freedesktop.org>
Subject: Re: mm/huge_memory: do not clobber swp_entry_t during THP split
Date: Tue, 25 Oct 2022 20:35:15 -0700 (PDT) [thread overview]
Message-ID: <3c785c89-e2d1-88bc-cdd6-14e8602c6fb4@google.com> (raw)
In-Reply-To: <20221025200417.4657a50e93cf13fb08a87db4@linux-foundation.org>
On Tue, 25 Oct 2022, Andrew Morton wrote:
> On Tue, 25 Oct 2022 11:03:38 +0100 Mel Gorman <mgorman@techsingularity.net> wrote:
>
> > > If so I
> > > can temporarily put it in until it arrives via the next rc - assuming that
> > > would be the flow from upstream pov?
> > >
> >
> > I expect it to. It's currently in the akpm/mm.git branch
> > mm/mm-hotfixes-unstable where I expect it to flow to mm/mm-hotfixes-stable
> > in due course before sending to Linus. I can't make promises about the
> > timing as that's determined by Andrew.
>
> This is now in mainline, 71e2d666ef85.
No, that one is Mel's commit, which GregKH already picked up for stable.
But what we're waiting for here is my fix to the warning that brings,
my fix currently lurking in mm-hotfixes-unstable as
45ba9c269874 ("mm: prep_compound_tail() clear page->private")
Hugh
prev parent reply other threads:[~2022-10-26 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 13:04 Tvrtko Ursulin
2022-10-24 14:23 ` Mel Gorman
2022-10-25 8:50 ` Tvrtko Ursulin
2022-10-25 10:03 ` Mel Gorman
2022-10-25 15:26 ` Hugh Dickins
2022-10-26 9:25 ` Mel Gorman
2022-10-26 3:04 ` Andrew Morton
2022-10-26 3:35 ` Hugh Dickins [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=3c785c89-e2d1-88bc-cdd6-14e8602c6fb4@google.com \
--to=hughd@google.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=matthew.auld@intel.com \
--cc=mgorman@techsingularity.net \
--cc=tvrtko.ursulin@linux.intel.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