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

[John Garry]

> > > 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.
>
> Sure, that make sense.
>
> > count the core set flags from 31 down, and limit IOMAP_F_PRIVATE to a
> > single flag, which is how it is used.
>
> flags in struct iomap is of type u16. So will make core iomap flags
> starting from bit 15, moving downwards.
>
> Here is a diff of what I think you meant - let me know if this diff
> looks good to you?

This is still outstanding, and it would be nice to fix this ASAP.

How about we go to 32b and change IOMAP_F_PRIVATE for v6.16, while just 
fix as suggested originally (by renumbering) for v6.15?