linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Harry Yoo <harry.yoo@oracle.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: stable@vger.kernel.org, Liam.Howlett@oracle.com,
	akpm@linux-foundation.org, baohua@kernel.org,
	baolin.wang@linux.alibaba.com, dev.jain@arm.com,
	hughd@google.com, jane.chu@oracle.com, jannh@google.com,
	kas@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org,
	lorenzo.stoakes@oracle.com, npache@redhat.com, pfalcato@suse.de,
	ryan.roberts@arm.com, vbabka@suse.cz, ziy@nvidia.com
Subject: Re: [PATCH V2 5.15.y 0/2] Fix bad pmd due to race between change_prot_numa() and THP migration
Date: Wed, 7 Jan 2026 12:28:06 +0900	[thread overview]
Message-ID: <aV3SxoHzSy-5vo69@hyeyoo> (raw)
In-Reply-To: <6e17dab8-cc85-4d68-a7b0-c187754572df@kernel.org>

On Tue, Jan 06, 2026 at 07:47:54PM +0100, David Hildenbrand (Red Hat) wrote:
> On 1/6/26 15:57, Harry Yoo wrote:
> > On Tue, Jan 06, 2026 at 03:35:32PM +0100, David Hildenbrand (Red Hat) wrote:
> > > On 1/6/26 12:50, Harry Yoo wrote:
> > > > V1 -> V2:
> > > >     - Because `pmd_val` variable broke ppc builds due to its name,
> > > >       renamed it to `_pmd`. see [1].
> > > >       [1] https://lore.kernel.org/stable/aS7lPZPYuChOTdXU@hyeyoo
> > > > 
> > > 
> > > Ouch.
> > 
> > Haha, it was really unexpected :)
> > 
> > > >     - Added David Hildenbrand's Acked-by [2], thanks a lot!
> > > >       [2] https://lore.kernel.org/linux-mm/ac8d7137-3819-4a75-9dd3-fb3d2259ebe4@kernel.org/
> > > 
> > > LGTM
> > 
> > Thanks!
> > 
> > Perhaps I should have clarified if your Acked-by:
> > applies only to 6.1.y or ealier versions as well (5.15.y, 5.10.y, 5.4.y).
> > 
> > What do you think?
> > (planning to send 5.10.y and 5.4.y versions tomorrow)
> 
> I don't expect there to be a lot of difference, so feel free to slap them on
> all, and I'll briefly scan the patches when you send them around.

Gotcha, and just sent it.
Thanks a lot!

-- 
Cheers,
Harry / Hyeonggon


      reply	other threads:[~2026-01-07  3:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 11:50 Harry Yoo
2026-01-06 11:50 ` [PATCH V2 5.15.y 1/2] mm/mprotect: use long for page accountings and retval Harry Yoo
2026-01-08 13:56   ` Patch "mm/mprotect: use long for page accountings and retval" has been added to the 5.15-stable tree gregkh
2026-01-06 11:50 ` [PATCH V2 5.15.y 2/2] mm/mprotect: delete pmd_none_or_clear_bad_unless_trans_huge() Harry Yoo
2026-01-08 13:56   ` Patch "mm/mprotect: delete pmd_none_or_clear_bad_unless_trans_huge()" has been added to the 5.15-stable tree gregkh
2026-01-06 14:35 ` [PATCH V2 5.15.y 0/2] Fix bad pmd due to race between change_prot_numa() and THP migration David Hildenbrand (Red Hat)
2026-01-06 14:57   ` Harry Yoo
2026-01-06 18:47     ` David Hildenbrand (Red Hat)
2026-01-07  3:28       ` Harry Yoo [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=aV3SxoHzSy-5vo69@hyeyoo \
    --to=harry.yoo@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=hughd@google.com \
    --cc=jane.chu@oracle.com \
    --cc=jannh@google.com \
    --cc=kas@kernel.org \
    --cc=lance.yang@linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=pfalcato@suse.de \
    --cc=ryan.roberts@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    --cc=ziy@nvidia.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