linux-kernel - Re: [PATCH 3/3] iomap: rework IOMAP atomic flags

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: <811387e4-eee2-4e68-91e1-e0a56671c5ff@oracle.com>
Date: Sun, 23 Mar 2025 13:07:21 +0000
From: John Garry <john.g.garry@...cle.com>
To: Christoph Hellwig <hch@....de>, Ritesh Harjani <ritesh.list@...il.com>
Cc: brauner@...nel.org, djwong@...nel.org, linux-fsdevel@...r.kernel.org,
        dchinner@...hat.com, linux-xfs@...r.kernel.org,
        linux-kernel@...r.kernel.org, ojaswin@...ux.ibm.com,
        martin.petersen@...cle.com, tytso@....edu, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 3/3] iomap: rework IOMAP atomic flags

On 23/03/2025 06:38, Christoph Hellwig wrote:
> On Sun, Mar 23, 2025 at 01:17:08AM +0530, Ritesh Harjani wrote:

@ Ritesh, thanks for the notice - are you ok to send a fix for this? At 
a glance, it seems that those two conflicting flags won't cross paths in 
practice (but obvs still need to fix this).

> 
> [full quote deleted, can you please properly trim your replies?]
> 
>> So, I guess we can shift IOMAP_F_SIZE_CHANGED and IOMAP_F_STALE by
>> 1 bit. So it will all look like..
> 
> Let's create some more space to avoid this for the next round, e.g.
> count the core set flags from 31 down, and limit IOMAP_F_PRIVATE to a
> single flag, which is how it is used.
>