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: <CAJ-ks9kiAH5MYmMvHxwH9JfBdhLGA_mP+ezmZ8wJOzDY1p7o5w@mail.gmail.com>
Date: Wed, 9 Oct 2024 16:51:19 -0400
From: Tamir Duberstein <tamird@...il.com>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Matthew Wilcox <willy@...radead.org>, Jonathan Corbet <corbet@....net>, linux-fsdevel@...r.kernel.org, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] XArray: minor documentation improvements

On Wed, Oct 9, 2024 at 4:44 PM Darrick J. Wong <djwong@...nel.org> wrote:
>
> n00b question: is xa_store(..., NULL) the same as xa_erase?
>
> If it is, then should the documentation mention that xa_store(NULL) is
> the same as xa_erase, and that both of these operations will cause the
> xarray to forget about that range?

They're not quite the same in the presence of `XA_FLAGS_ALLOC`. Per the docs:

> Unlike a normal XArray, storing NULL will mark the entry as being in use [...]

See https://docs.kernel.org/core-api/xarray.html#allocating-xarrays.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ