Christoph Hellwig <hch@xxxxxxxxxxxxx> writes: > So why do you add tracepoints in ext2 in addition to iomap? 1. It's very convenient to look into all ext2 filesystem activity by just "trace-cmd -e ext2" 2. For cases in ext2 which fallbacks to buffered-io routine. Adding a trace point specifically for ext2 can cover this path as well as to how much got written via buffered-io path or in case there was an error while doing that. 3. As of now there was no tracepoint added to ext2. Going forward it will be quick and convenient to add any trace event for debugging/observing other call paths too while development. -ritesh
