On Thu, Feb 22, 2024 at 09:48:17PM -0800, Darrick J. Wong wrote: > From: Darrick J. Wong <djwong@xxxxxxxxxx> > > Per the comment in the error case of xfs_reflink_recover_cow, zero out > any error (after shutting down the log) so that we actually kill any new > intent items that might have gotten logged by later recovery steps. > Discovered by xfs/434, which few people actually seem to run. Talking about xfs/434, it just caused me some nasty debugging headache last week. It is the first of only three tests requiring a loadable xfs module, and when there is an xfs.ko for the uname around but xfs is built into the kernel as it is for my usual test configs it fails in completely weird and hard to debug ways. The fact that it requires a modular xfs might also be the reason why it's rarely run. The fix itself looks good: Reviewed-by: Christoph Hellwig <hch@xxxxxx>
