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: <c456ebdf-b75e-1f84-c097-f294b954c572@google.com>
Date: Mon, 12 Aug 2024 19:32:46 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Danilo Krummrich <dakr@...nel.org>
cc: akpm@...ux-foundation.org, cl@...ux.com, penberg@...nel.org, 
    iamjoonsoo.kim@....com, vbabka@...e.cz, roman.gushchin@...ux.dev, 
    42.hyeyoo@...il.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 2/2] mm: krealloc: clarify valid usage of __GFP_ZERO

On Tue, 13 Aug 2024, Danilo Krummrich wrote:

> Properly document that if __GFP_ZERO logic is requested, callers must
> ensure that, starting with the initial memory allocation, every
> subsequent call to this API for the same memory allocation is flagged
> with __GFP_ZERO. Otherwise, it is possible that __GFP_ZERO is not fully
> honored by this API.
> 
> Signed-off-by: Danilo Krummrich <dakr@...nel.org>

Acked-by: David Rientjes <rientjes@...gle.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ