All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	thomas.petazzoni@bootlin.com, Hao Ge <hao.ge@linux.dev>,
	Suren Baghdasaryan <surenb@google.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Miguel Gazquez <miguel.gazquez@bootlin.com>
Subject: Re: [PATCH 6.12.y] mm/alloc_tag: clear codetag for pages allocated before page_ext initialization
Date: Sun, 26 Jul 2026 08:04:53 -0400	[thread overview]
Message-ID: <20260725192000.stable-0014@kernel.org> (raw)
In-Reply-To: <20260724080327.2337330-1-miguel.gazquez@bootlin.com>

> commit 6b1842775a460245e97d36d3a67d0cfba7c4ff79 upstream.

Thanks for the backport, but this won't build on 6.12 - it uses several
APIs that only exist from v6.13-rc1 onward:

 - clear_early_alloc_pfn_tag_refs() uses the 3-arg
   get_page_tag_ref(page, &ref, &handle) plus update_page_tag_ref() and
   union pgtag_ref_handle; 6.12 only has the 1-arg get_page_tag_ref()
   returning a union codetag_ref *.
 - alloc_tag_set_inaccurate() does not exist in 6.12.
 - the mem_profiling_compressed static key does not exist in 6.12.
 - is_codetag_empty(&ref) passes a double pointer, since 6.12's ref is
   already a union codetag_ref * (should be is_codetag_empty(ref)).

Could you respin a v2 adapted to the 6.12 page-tag-ref API? Thanks.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-07-26 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 11:01 FAILED: patch "[PATCH] mm/alloc_tag: clear codetag for pages allocated before" failed to apply to 6.12-stable tree gregkh
2026-07-24  8:03 ` [PATCH 6.12.y] mm/alloc_tag: clear codetag for pages allocated before page_ext initialization Miguel Gazquez
2026-07-26 12:04   ` Sasha Levin [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=20260725192000.stable-0014@kernel.org \
    --to=sashal@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.ge@linux.dev \
    --cc=kent.overstreet@linux.dev \
    --cc=miguel.gazquez@bootlin.com \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=thomas.petazzoni@bootlin.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.