All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, surenb@google.com,
	stable@vger.kernel.org, rppt@kernel.org, pratyush@kernel.org,
	pasha.tatashin@soleen.com, graf@amazon.com,
	ran.xiaokai@zte.com.cn
Subject: Re: [merged mm-hotfixes-stable] kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch removed from -mm tree
Date: Tue, 20 Jan 2026 15:24:06 +0000	[thread overview]
Message-ID: <2vxzqzrke295.fsf@kernel.org> (raw)
In-Reply-To: <20260119203054.70AE8C116C6@smtp.kernel.org> (Andrew Morton's message of "Mon, 19 Jan 2026 12:30:53 -0800")

Hi Andrew,

On Mon, Jan 19 2026, Andrew Morton wrote:

> The quilt patch titled
>      Subject: kho: init alloc tags when restoring pages from reserved memory
> has been removed from the -mm tree.  Its filename was
>      kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch
>
> This patch was dropped because it was merged into the mm-hotfixes-stable branch
> of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

This patch isn't quite complete. See [0]. It doesn't do anything wrong,
it just doesn't fix the problem for every case.

I suggested a re-roll of this patch based on top of my cleanup patches
[1], since I think with those the end result is a bit nicer.

I suppose we have 3 options:

1. Take this patch in hotfixes and leave kho_restore_pages() path
   unfixed. The fix the rest next merge window.

2. Do a new version of this patch fixing kho_restore_pages() with the
   current code, and then re-roll the clean up series to fix conflicts
   for next merge window.

3. Pull in the cleanups in hotfixes too, and then do a new revision of
   this patch on top.

I don't think the end result of option 2 is too horrible, so I think
that is probably the best option, but do let me know what you'd prefer.

[0] https://lore.kernel.org/linux-mm/2vxzpl7chw8d.fsf@kernel.org/
[1] https://lore.kernel.org/linux-mm/20260116112217.915803-1-pratyush@kernel.org/T/#u

>
> ------------------------------------------------------
> From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> Subject: kho: init alloc tags when restoring pages from reserved memory
> Date: Fri, 9 Jan 2026 10:42:51 +0000
>
> Memblock pages (including reserved memory) should have their allocation
> tags initialized to CODETAG_EMPTY via clear_page_tag_ref() before being
> released to the page allocator.  When kho restores pages through
> kho_restore_page(), missing this call causes mismatched
> allocation/deallocation tracking and below warning message:
>
> alloc_tag was not set
> WARNING: include/linux/alloc_tag.h:164 at ___free_pages+0xb8/0x260, CPU#1: swapper/0/1
> RIP: 0010:___free_pages+0xb8/0x260
>  kho_restore_vmalloc+0x187/0x2e0
>  kho_test_init+0x3c4/0xa30
>  do_one_initcall+0x62/0x2b0
>  kernel_init_freeable+0x25b/0x480
>  kernel_init+0x1a/0x1c0
>  ret_from_fork+0x2d1/0x360
>
> Add missing clear_page_tag_ref() annotation in kho_restore_page() to
> fix this.
>
> Link: https://lkml.kernel.org/r/20260113033403.161869-1-ranxiaokai627@163.com
> Link: https://lkml.kernel.org/r/20260109104251.157767-1-ranxiaokai627@163.com
> Fixes: fc33e4b44b27 ("kexec: enable KHO support for memory preservation")
> Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Reviewed-by: Suren Baghdasaryan <surenb@google.com>
> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> Cc: Alexander Graf <graf@amazon.com>
> Cc: Pratyush Yadav <pratyush@kernel.org>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  kernel/liveupdate/kexec_handover.c |    1 +
>  1 file changed, 1 insertion(+)
>
> --- a/kernel/liveupdate/kexec_handover.c~kho-init-alloc-tags-when-restoring-pages-from-reserved-memory
> +++ a/kernel/liveupdate/kexec_handover.c
> @@ -255,6 +255,7 @@ static struct page *kho_restore_page(phy
>  	if (is_folio && info.order)
>  		prep_compound_page(page, info.order);
>  
> +	clear_page_tag_ref(page);
>  	adjust_managed_page_count(page, nr_pages);
>  	return page;
>  }
> _
>
> Patches currently in -mm which might be from ran.xiaokai@zte.com.cn are
>
> alloc_tag-fix-rw-permission-issue-when-handling-boot-parameter.patch
>

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-01-20 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 20:30 [merged mm-hotfixes-stable] kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch removed from -mm tree Andrew Morton
2026-01-20 15:24 ` Pratyush Yadav [this message]
2026-01-20 17:36   ` Andrew Morton
2026-01-21 10:06     ` Pratyush Yadav
  -- strict thread matches above, loose matches on Subject: below --
2026-01-27  2:57 Andrew Morton

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=2vxzqzrke295.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=graf@amazon.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=ran.xiaokai@zte.com.cn \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@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 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.