If trace-cmd record is called to write to a file that is on a filesystem, it fails: trace-cmd: Invalid argument recorder error in splice output CPU0 data recorded at offset=0x2bd000 0 bytes in size (single-core system because this was ARCH=um) and while it actually creates a trace.dat file, it ends up being empty. It should instead detect that situation and fall back to read/write if splice doesn't work.
Created attachment 301119 [details] Verify that splice works before using splice I do not have any file systems available to me that does not work with splice. Can you test this patch to see if it switches over to read/write properly if the source directory does not handle splice? Thanks, -- Steve