All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, vbabka@suse.cz,
	stable@vger.kernel.org, joe.liu@mediatek.com,
	mgorman@techsingularity.net
Subject: Re: + mm-page_alloc-free-pages-to-correct-buddy-list-after-pcp-lock-contention.patch added to mm-hotfixes-unstable branch
Date: Tue, 12 Sep 2023 12:56:25 -0400	[thread overview]
Message-ID: <20230912165625.GA34089@cmpxchg.org> (raw)
In-Reply-To: <20230912090938.c5314956fe385241bf567a9e@linux-foundation.org>

On Tue, Sep 12, 2023 at 09:09:38AM -0700, Andrew Morton wrote:
> On Tue, 12 Sep 2023 09:50:29 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
> 
> > > Cc: Johannes Weiner <hannes@cmpxchg.org>
> > > Cc: <stable@vger.kernel.org>
> > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > 
> > This patch is superseded by the following patch you picked up:
> > mm-page_alloc-fix-cma-and-highatomic-landing-on-the-wrong-buddy-list.patch
> 
> OK.
> 
> > If you drop this patch here, you can also drop the fixlet to
> > free_unref_page(). The branch in there should look like this:
> > 
> > 	if (pcp)
> > 		free_unref_page_commit(..., pcpmigratetype, ...);
> > 	else
> > 		free_one_page(..., migratetype, ...);
> 
> Well kinda.  It's actually
> 
> 	if (pcp) {
> 		free_unref_page_commit(zone, pcp, page, migratetype, order);

							^^ pcpmigratetype

is what I was trying to highlight.

But yes, the pcp_spin_unlock() is needed too!

> 		pcp_spin_unlock(pcp);
> 	} else {
> 		free_one_page(zone, page, pfn, order, migratetype, FPI_NONE);
> 	}
> 

      reply	other threads:[~2023-09-12 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 21:00 + mm-page_alloc-free-pages-to-correct-buddy-list-after-pcp-lock-contention.patch added to mm-hotfixes-unstable branch Andrew Morton
2023-09-12 13:50 ` Johannes Weiner
2023-09-12 16:09   ` Andrew Morton
2023-09-12 16:56     ` Johannes Weiner [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=20230912165625.GA34089@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=joe.liu@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mm-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.