[LU-16605] lfs fid2path should allow null byte separated output

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Affects Version/s: Upstream
• Labels: easy lug23dd
• Severity: 3
• Assignee: Arshad Hussain
• Reporter: Simon Westersund

Description

When using 'lfs fid2path' to find all hardlinks of a FID, the links are printed out with newline characters separating them. This is unsafe, since file paths are allowed to contain newline characters as well, which makes fid2path unreliable for non-interactive use (i.e. as part of other tools, without human supervision).

This issue is present in the master branch, so I assume it might affect all current versions.

To mitigate this problem and not break backwards compatibility, perhaps one could add a new command line argument that changes the path separator from '\n' to '\0'? Similar to "find . -print0", for example.

# Suggested usage:
lfs fid2path -0 <FID>