Re: [PATCH v3 0/2] mm/huge_memory: fix the copy of special PMDs at fork

[Konstantin Khorenko <khorenko@virtuozzo.com>]

On 10/14/26 18:04, Lance Yang wrote:
> On 2026/10/14 23:57, Zi Yan wrote:
>> On 14 Oct 2026, at 11:46, Konstantin Khorenko wrote:
>>
>> <snip>
>>
>>> Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
>>> ---
>>> Changes in v3:
>>> - Patch 1: recheck the PMD with pmd_none(), as only a zap can change
>>>    it and a zap leaves it none (Lance Yang).
>>> - Link to v2: https://patch.msgid.link/20261014-b4-prep-vstor-149847-copy_huge_pmd-recheck-special-pmd-v2-0-e1548488fa68@virtuozzo.com
>>>
>>> Changes in v2:
>>> - Add patch 2, the page table deposit for ppc64 hash, reported by
>>>    Sashiko.
>>> - Patch 1: name panthor instead of drm_gem_shmem as the driver whose
>>>    stale child mapping reaches freed pages: drm_gem_shmem keeps the
>>>    pages of a purged object until the last mapping goes away.
>>> - Link to v1: https://patch.msgid.link/20261014-b4-prep-vstor-149847-copy_huge_pmd-recheck-special-pmd-v1-1-d225c60bc316@virtuozzo.com
>>>
>>
>> Please stop sending new versions of a patchset repeatedly.
>> Wait at least a day for others to catch up.
> 
> +1
> 
> Please slow down a bit. You don't need to respin every few
> hours. That just makes everyone start over ...
> 
> Post a version, wait for feedback, then revise. Twice a week
> is plenty, honestly :)

Guys, you are awesome. :)

Trying myself to do the very best i can and yes,
"too many and too fast" sometime does not leads to the "very best" result.
Set myself a hard upper limit to 1 rework per week. :)

Have a nice day and thank you for looking into this!

Cheers, Konstantin