linux-kernel - Re: [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue

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] [day] [month] [year] [list]

Message-ID: <d46f66b3-cb3e-458a-ba98-508389a601ed@vivo.com>
Date:   Wed, 22 Nov 2023 15:10:30 +0800
From:   zhiguojiang <justinjiang@...o.com>
To:     Matthew Wilcox <willy@...radead.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
        opensource.kernel@...o.com
Subject: Re: [PATCH v3] mm: ALLOC_HIGHATOMIC flag allocation issue



在 2023/11/22 14:20, Matthew Wilcox 写道:
> On Wed, Nov 22, 2023 at 09:39:25AM +0800, Zhiguo Jiang wrote:
>> Update base on the latest Linus' tree or Andrew's tree.
>> +++ b/mm/page_alloc.c
>> @@ -2851,9 +2851,9 @@ struct page *__rmqueue_pcplist(struct zone *zone, unsigned int order,
>>   			int alloced;
>>   
>>   			/*
>> -			 * If pcplist is empty and alloc_flags is with ALLOC_HIGHATOMIC,
>> -			 * it should alloc from buddy highatomic migrate freelist firstly
>> -			 * to ensure quick and successful allocation.
>> +			 * If pcplist is empty and alloc_flags contains
>> +			 * ALLOC_HIGHATOMIC, alloc from buddy highatomic
>> +			 * freelist first.
> No, it's still based on your earlier patch,  is it really so hard for
> you to read your patches before you send them?
Sorry, I didn't understand your meaning correctly before. I have updated 
base on the latest linux-next tree in patch v4.
Thank you for your patient guidance.