All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zi Yan" <ziy@nvidia.com>
To: "Sasha Levin" <sashal@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>
Cc: <stable@vger.kernel.org>,
	"Baolin Wang" <baolin.wang@linux.alibaba.com>,
	"Lorenzo Stoakes" <ljs@kernel.org>,
	"Barry Song" <baohua@kernel.org>,
	"David Hildenbrand" <david@kernel.org>,
	"Dev Jain" <dev.jain@arm.com>,
	"Lance Yang" <lance.yang@linux.dev>,
	"Liam R . Howlett" <liam@infradead.org>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Ryan Roberts" <ryan.roberts@arm.com>,
	"William Kucharski" <william.kucharski@oracle.com>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.6.y] mm/huge_memory: use folio's memcg inside __folio_split()
Date: Sat, 12 Sep 2026 14:31:38 -0400	[thread overview]
Message-ID: <DLDJWF5NE46Z.3JBTVOKAYOYGU@nvidia.com> (raw)
In-Reply-To: <daily-reply-0014-re-huge-memory-6-6-ask-6-12@kernel.org>

On Sat Sep 12, 2026 at 11:26 AM EDT, Sasha Levin wrote:
> Thanks for the review, Johannes.
>
> I'm holding the 6.6.y patch for now, because 6.12.y needs this first.
> c299a2285d9d ("mm/huge_memory: use folio's memcg inside
> __folio_split()") is absent from 6.12.y, and we don't queue a fix on an
> older tree while a newer one still lacks it.
>
> 6.12.y also needs its own version rather than this one. I tried your 6.6.y
> patch against it and it fails at mm/huge_memory.c:2646. The two trees have
> different shapes here: 6.6.y has split_huge_page_to_list(page, list) using
> XA_STATE, while 6.12.y has split_huge_page_to_list_to_order(page, list,
> new_order) using XA_STATE_ORDER.
>
> Zi Yan, could you send a 6.12.y backport? Once that one is in I'll take
> both together.

Done. See https://lore.kernel.org/all/20260912182926.1326147-1-ziy@nvidia.com/

BTW, I see you also sent one[1], but it seems that it is using a
non-existing get_mem_cgroup_from_folio(). What is that for? Thanks.

[1] https://lore.kernel.org/all/20260903223027.1739434-1-sashal@kernel.org/


-- 
Best Regards,
Yan, Zi


  reply	other threads:[~2026-09-12 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 10:46 FAILED: patch "[PATCH] mm/huge_memory: use folio's memcg inside __folio_split()" failed to apply to 6.6-stable tree gregkh
2026-09-04  2:26 ` [PATCH 6.6.y] mm/huge_memory: use folio's memcg inside __folio_split() Zi Yan
2026-09-06 13:33   ` Sasha Levin
2026-09-06 22:46     ` Zi Yan
2026-09-08  0:53       ` Sasha Levin
2026-09-10 19:23       ` Johannes Weiner
2026-09-12 15:26         ` Sasha Levin
2026-09-12 18:31           ` Zi Yan [this message]
2026-09-15  2:03             ` Sasha Levin
2026-09-04  2:36 ` Sasha Levin

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=DLDJWF5NE46Z.3JBTVOKAYOYGU@nvidia.com \
    --to=ziy@nvidia.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=hannes@cmpxchg.org \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=ljs@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.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 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.