linux-kernel - Re: [PATCH v4 4/6] mm/huge_memory: convert VM_BUG* to VM_WARN* in __folio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <F7FAD17A-9F00-411E-9B12-D38699534D18@nvidia.com>
Date: Fri, 18 Jul 2025 10:48:54 -0400
From: Zi Yan <ziy@...dia.com>
To: David Hildenbrand <david@...hat.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, linux-mm@...ck.org,
 Andrew Morton <akpm@...ux-foundation.org>,
 Dan Carpenter <dan.carpenter@...aro.org>,
 Antonio Quartulli <antonio@...delbit.com>, Hugh Dickins <hughd@...gle.com>,
 Kirill Shutemov <k.shutemov@...il.com>,
 Baolin Wang <baolin.wang@...ux.alibaba.com>,
 "Liam R. Howlett" <Liam.Howlett@...cle.com>, Nico Pache <npache@...hat.com>,
 Ryan Roberts <ryan.roberts@....com>, Dev Jain <dev.jain@....com>,
 Barry Song <baohua@...nel.org>, Balbir Singh <balbirs@...dia.com>,
 Matthew Brost <matthew.brost@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 4/6] mm/huge_memory: convert VM_BUG* to VM_WARN* in
 __folio_split.

On 18 Jul 2025, at 3:22, David Hildenbrand wrote:

> On 18.07.25 04:29, Zi Yan wrote:
>> These VM_BUG* can be handled gracefully without crashing kernel.
>>
>> Signed-off-by: Zi Yan <ziy@...dia.com>
>> ---
>>   mm/huge_memory.c | 16 +++++++++++++---
>>   1 file changed, 13 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index d36f7bdaeb38..d6ff5e8c89d7 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -3601,8 +3601,14 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
>>   	pgoff_t end;
>>   	bool is_hzp;
>>  -	VM_BUG_ON_FOLIO(!folio_test_locked(folio), folio);
>> -	VM_BUG_ON_FOLIO(!folio_test_large(folio), folio);
>> +	if (!folio_test_locked(folio)) {
>> +		VM_WARN_ON_ONCE_FOLIO(1, folio);
>> +		return -EINVAL;
>> +	}
>> +	if (!folio_test_large(folio)) {
>> +		VM_WARN_ON_ONCE_FOLIO(1, folio);
>> +		return -EINVAL;
>> +	}
>
> For cases that we handle gracefully you usually want to use
>
> if (WARN_ON_ONCE(..))

Got it.

>
> because then you get actually notified when that unexpected thing happens.
>
> I am not really sure if recovery is warranted here: smells like a straight VM_WARN_ON_ONCE_FOLIO() is sufficient, and catching this early during development that something is extremely off.

OK. I will update it to just VM_WARN_ON_ONCE_FOLIO().

Thanks.

Best Regards,
Yan, Zi