From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>, Zi Yan <ziy@nvidia.com>,
david@kernel.org, lorenzo.stoakes@oracle.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org
Subject: Re: [Patch v3 2/2] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported()
Date: Fri, 21 Nov 2025 09:00:48 +0000 [thread overview]
Message-ID: <20251121090048.3n25tjhusu45xpoo@master> (raw)
In-Reply-To: <20251120131621.486cbccc8a713ddbd30dcfe6@linux-foundation.org>
On Thu, Nov 20, 2025 at 01:16:21PM -0800, Andrew Morton wrote:
>On Wed, 19 Nov 2025 00:52:48 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> >> Hi Andrew,
>> >>
>> >> This patch does not fix the NULL dereferencing issue yet. Wei is going to
>> >> 1. send a patch to fix the bug on top of mm-stable,
>> >> 2. resend this patchset on top of the fix in 1.
>> >>
>> >> This might be easier for back porting the fix. Maybe you can drop this series
>> >> for now.
>> >>
>> >> Wei, do you agree?
>> >
>> >Dropping this series messes up later patches. I could of course redo
>> >things but would prefer a fixed up version of this patchset asap, please.
>>
>> Ok, i will prepare a fixed on top of this.
>
>Did this happen?
>
>I remain unclear on the status of this small series. Issues which I
>have flagged are:
>
>https://lkml.kernel.org/r/20251118021047.uyldr7aay6fb5evt@master
>https://lkml.kernel.org/r/136E8B1C-3352-412C-8038-627F5CC8A112@nvidia.com
>https://lkml.kernel.org/r/20251117012239.lqm33uu4vl4y5zqc@master
>https://lkml.kernel.org/r/337CD281-F5B3-47FE-82C3-ECB236450F60@nvidia.com
>
There are two related topic:
1. A null pointer dereference bug:
https://lkml.kernel.org/r/20251118021047.uyldr7aay6fb5evt@master
https://lkml.kernel.org/r/20251117012239.lqm33uu4vl4y5zqc@master
https://lkml.kernel.org/r/337CD281-F5B3-47FE-82C3-ECB236450F60@nvidia.com
This three mail are related to the bug, which is fixed in :
http://lkml.kernel.org/r/20251119235302.24773-1-richard.weiyang@gmail.com
Currently looks good, and will do backport when necessary.
2. A further cleanup attempt:
https://lkml.kernel.org/r/136E8B1C-3352-412C-8038-627F5CC8A112@nvidia.com
This one is the related mail.
I proposed one version in
http://lkml.kernel.org/r/20251114075703.10434-1-richard.weiyang@gmail.com
But it is not proper, will do follow up work later.
>and a couple of comments from yourself indicating that updates are
>required.
>
>Have all these things now been addressed?
Hope it is clear now :-)
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-11-21 9:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 3:41 [Patch v3 0/2] mm/huge_memory: Define split_type and consolidate split support checks Wei Yang
2025-11-06 3:41 ` [Patch v3 1/2] mm/huge_memory: introduce enum split_type for clarity Wei Yang
2025-11-06 10:17 ` David Hildenbrand (Red Hat)
2025-11-06 14:57 ` Wei Yang
2025-11-07 0:44 ` Zi Yan
2025-11-06 3:41 ` [Patch v3 2/2] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported() Wei Yang
2025-11-06 10:20 ` David Hildenbrand (Red Hat)
2025-11-07 0:46 ` Zi Yan
2025-11-07 1:17 ` Wei Yang
2025-11-07 2:07 ` Zi Yan
2025-11-07 2:49 ` Wei Yang
2025-11-07 3:21 ` Zi Yan
2025-11-07 7:29 ` Wei Yang
2025-11-14 3:03 ` Wei Yang
2025-11-17 1:22 ` Wei Yang
2025-11-17 15:56 ` Zi Yan
2025-11-18 2:10 ` Wei Yang
2025-11-18 3:33 ` Wei Yang
2025-11-18 4:10 ` Zi Yan
2025-11-18 18:32 ` Andrew Morton
2025-11-18 18:55 ` Zi Yan
2025-11-18 22:06 ` Andrew Morton
2025-11-19 0:52 ` Wei Yang
2025-11-20 21:16 ` Andrew Morton
2025-11-21 0:55 ` Zi Yan
2025-11-21 9:00 ` Wei Yang [this message]
2025-11-21 14:59 ` Zi Yan
2025-11-21 16:50 ` Andrew Morton
2025-11-21 17:00 ` Zi Yan
2025-11-21 18:39 ` Andrew Morton
2025-11-21 19:09 ` Zi Yan
2025-11-21 19:15 ` 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=20251121090048.3n25tjhusu45xpoo@master \
--to=richard.weiyang@gmail.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=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--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 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.