The issue arises from the mechanism introduced to prevent a write hole of an extent buffer in the Btrfs file system. When `btrfs clear buffer dirty()` marks an extent buffer as `EXTENT BUFFER ZONED ZEROOUT` and skips the entry function, it can lead to two problems if this call happens while the buffer is under IO (with the `WRITEBACK` flag set, without the `DIRTY` flag). Firstly, it can result in adding a faulty delayed reference item, leading to a file system corrupted (EUCLEAN) error. Secondly, it can write out a cleared tree node on disk. However, the chance of hitting the corruption is relatively small because the corrupted node will be invalidated in the next transaction commit anyway.