From: Wei Yang <richard.weiyang@gmail.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>, Zi Yan <ziy@nvidia.com>,
Linux MM <linux-mm@kvack.org>
Subject: Re: A potential refcount issue during __folio_split
Date: Mon, 2 Mar 2026 09:02:10 +0000 [thread overview]
Message-ID: <20260302090210.mssx5sdq7qrjr2yv@master> (raw)
In-Reply-To: <fdff3384-d62b-403f-a89a-f32abdaabe63@kernel.org>
On Mon, Mar 02, 2026 at 09:01:05AM +0100, David Hildenbrand (Arm) wrote:
>On 3/2/26 00:59, Wei Yang wrote:
>> On Mon, Feb 23, 2026 at 11:00:01PM -0500, Zi Yan wrote:
>>> On 23 Feb 2026, at 6:59, Wei Yang wrote:
>>>
>>>>
>>>> Missed this. Agree.
>>>>
>>>>
>>>> I am afraid it would be complicated?
>>>>
>>>> Well, we don't have this usecase now, could decide it when we do need it.
>>>
>>> The patch below should work, but for now, since we do not have any user,
>>> it is better to update the comment and add a check to make sure @lock_at
>>> always points to the head page if @list is not NULL.
>>>
>>
>> Hi, Zi Yan
>>
>> Just want to confirm what we prefer to do now. We have three options:
>>
>> 1) update comment and a check on @lock_at
>> 2) fix it as you proposed below
>> 3) do nothing for now
>
>I'd go with 3).
>
Got it.
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2026-03-02 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260222010425.gbsjzhrew3pg4qrw@master>
[not found] ` <20260222010708.uohpmddmzaa4i4ic@master>
2026-02-22 3:00 ` Zi Yan
2026-02-22 10:28 ` Wei Yang
2026-02-23 9:23 ` David Hildenbrand (Arm)
2026-02-23 11:59 ` Wei Yang
2026-02-24 4:00 ` Zi Yan
2026-02-24 4:25 ` Wei Yang
2026-02-27 0:51 ` Wei Yang
2026-03-01 23:59 ` Wei Yang
2026-03-02 8:01 ` David Hildenbrand (Arm)
2026-03-02 9:02 ` Wei Yang [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=20260302090210.mssx5sdq7qrjr2yv@master \
--to=richard.weiyang@gmail.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--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