Hi all, This is a quick side quest based on the discussion on the iomap folio batch series here[1]. I could see this going a number of different ways and/or being enhanced in the future. For example, we could have per-tag warning state instead of the global op state, dynamic default configuration, put this behind a kconfig option, etc. My goal here is really just to implement enough to keep things simple and pretty close to existing XFS_DEBUG behavior. Ultimately if people are Ok with something like this, I'll change the force zero tag in the iomap series to on by default. If not, I'll just leave it as is and go with a custom test. Otherwise, this survives a first run through fstests without any explosions or spurious failures. Thoughts, reviews, flames appreciated. Brian [1] https://lore.kernel.org/linux-fsdevel/20250605173357.579720-8-bfoster@xxxxxxxxxx/ Brian Foster (3): xfs: support on by default errortags xfs: convert extent alloc debug fallback to errortag xfs: convert sparse inode alloc debug fallback to errortag fs/xfs/libxfs/xfs_alloc.c | 5 +--- fs/xfs/libxfs/xfs_errortag.h | 6 ++++- fs/xfs/libxfs/xfs_ialloc.c | 14 ++++------- fs/xfs/xfs_error.c | 48 ++++++++++++++++++++++++++++++++++-- fs/xfs/xfs_mount.h | 3 +++ 5 files changed, 60 insertions(+), 16 deletions(-) -- 2.49.0
