a recommendation to run fsck.hfsplus. This avoids
continuing RW operation with a known-bad allocator state.

In parallel, I plan to keep the -EEXIST change in hfs_bnode_create() as
a robustness fix for any remaining or future inconsistency paths.

I’ll post a respin shortly.

If you’re OK with it, I can also post the hfs_bnode_create() -EEXIST
change as a standalone fix, since it independently prevents a refcount
underflow and panic even outside the bitmap-corruption scenario. I’ll
continue working on the bitmap validation in parallel.

Thanks,
Shardul[PATCH v2 1/2] hfsplus: skip node 0 in hfs_bmap_allocShardul Bankar <shardul.b@mpiricsoftware.com> undefinedViacheslav Dubeyko <slava@dubeyko.com>, zippel@linux-m68k.org, linux-fsdevel@vger.kernel.org, glaubitz@physik.fu-berlin.de, frank.li@vivo.com undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefinedŒ$„Û