Linux MM tree latest commits
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, paulmck@kernel.org,
	jhubbard@nvidia.com, david@redhat.com
Subject: Re: + mm-fix-is_pinnable_page-against-on-cma-page-v5.patch added to mm-unstable branch
Date: Thu, 12 May 2022 14:34:45 -0700	[thread overview]
Message-ID: <Yn19dQ27lveQBOAw@google.com> (raw)
In-Reply-To: <Yn18AfcH26Rtry+/@google.com>

On Thu, May 12, 2022 at 02:28:33PM -0700, Minchan Kim wrote:
> On Thu, May 12, 2022 at 01:45:05PM -0700, Andrew Morton wrote:
> > 
> > The patch titled
> >      Subject: mm-fix-is_pinnable_page-against-on-cma-page-v5
> > has been added to the -mm mm-unstable branch.  Its filename is
> >      mm-fix-is_pinnable_page-against-on-cma-page-v5.patch
> > 
> > This patch will shortly appear at
> >      https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-fix-is_pinnable_page-against-on-cma-page-v5.patch
> > 
> > This patch will later appear in the mm-unstable branch at
> >     git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> > 
> > Before you just go and hit "reply", please:
> >    a) Consider who else should be cc'ed
> >    b) Prefer to cc a suitable mailing list as well
> >    c) Ideally: find the original patch on the mailing list and do a
> >       reply-to-all to that, adding suitable additional cc's
> > 
> > *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> > 
> > The -mm tree is included into linux-next via the mm-everything
> > branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> > and is updated there every 2-3 working days
> > 
> > ------------------------------------------------------
> > From: Minchan Kim <minchan@kernel.org>
> > Subject: mm-fix-is_pinnable_page-against-on-cma-page-v5
> > 
> >   * clarification why we need READ_ONCE - Paul
> >   * Add a comment about READ_ONCE - John
> > 
> > Link: https://lkml.kernel.org/r/20220512204143.3961150-1-minchan@kernel.org
> > Signed-off-by: Minchan Kim <minchan@kernel.org>
> > Cc: "Paul E . McKenney" <paulmck@kernel.org>
> > Cc: John Hubbard <jhubbard@nvidia.com>
> > Cc: David Hildenbrand <david@redhat.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> > 
> >  include/linux/mm.h |    9 +++++----
> >  1 file changed, 5 insertions(+), 4 deletions(-)
> > 
> > --- a/include/linux/mm.h~mm-fix-is_pinnable_page-against-on-cma-page-v5
> > +++ a/include/linux/mm.h
> > @@ -1627,13 +1627,14 @@ static inline bool is_pinnable_page(stru
> >  {
> >  #ifdef CONFIG_CMA
> >  	/*
> > -	 * use volatile to use local variable mt instead of
> > -	 * refetching mt value.
> > +	 * Defend against future compiler LTO features, or code refactoring
> > +	 * that inlines the above function, by forcing a single read. Because,
> > +	 * this routine races with set_pageblock_migratetype(), and we want to
> > +	 * avoid reading zero, when actually one or the other flags was set.
> >  	 */
> > -	int __mt = get_pageblock_migratetype(page);
> 
> It makes build failure.
> 
> Could you pick this up instead?
> 
> https://lore.kernel.org/all/Yn10GkInyZNtqASa@google.com/

I really don't understand why it works or don't sometimes
At least, it works 

https://lore.kernel.org/lkml/Yn10GkInyZNtqASa@google.com/
> 
> Sorry for confusing.

      reply	other threads:[~2022-05-12 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 20:45 + mm-fix-is_pinnable_page-against-on-cma-page-v5.patch added to mm-unstable branch Andrew Morton
2022-05-12 21:28 ` Minchan Kim
2022-05-12 21:34   ` Minchan Kim [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=Yn19dQ27lveQBOAw@google.com \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=paulmck@kernel.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