Re: [PATCH v5 10/17] mm/page-flags: check page/folio->private instead of PG_private

[Zi Yan <ziy@nvidia.com>]

>>
>>> diff --git a/tools/mm/page-types.c b/tools/mm/page-types.c
>>> index 7fc5a8be5997f..47e4781c5fc38 100644
>>> --- a/tools/mm/page-types.c
>>> +++ b/tools/mm/page-types.c
>>
>> [ ... ]
>>
>>> @@ -131,7 +130,6 @@ static const char * const page_flag_names[] = {
>>>  	[KPF_RESERVED]		= "r:reserved",
>>>  	[KPF_MLOCKED]		= "m:mlocked",
>>>  	[KPF_OWNER_2]		= "d:owner_2",
>>> -	[KPF_PRIVATE]		= "P:private",
>>>  	[KPF_PRIVATE_2]		= "p:private_2",
>>
>> [Severity: Medium]
>> Does removing the flag name from page_flag_names in page-types.c break
>> parsing tools relying on the P:private designation?
>
> Will send a separate patch to fix page-type.c

Misread the review. The change is intended. Any related parsing tool
needs to adapt to the change.

>
>>
>> -- 
>> Sashiko AI review · https://sashiko.dev/#/patchset/20260920-remove-pg_private-v5-0-bb68b6a21869@nvidia.com?part=10


Best Regards,
Yan, Zi