On Fri, 12 Feb 2021 at 14:21, Darrick J. Wong [off-list ref] wrote:

On Fri, Feb 12, 2021 at 01:55:06PM -0800, Markus Mayer wrote:

quoted

On Fri, 12 Feb 2021 at 13:29, Eric Sandeen [off-list ref] wrote:

quoted

On 2/12/21 2:51 PM, Markus Mayer wrote:

quoted

quoted

To prevent issues when the ".o" extension appears in a directory path,
ensure that the ".o" -> ".lo" substitution is only performed for the
final file extension.

If the subject should be "[PATCH] xfsprogs: ...", please let me know.

Nah, that's fine, I noticed it.

So did you have a path component that had ".o" in it that got substituted?
Is that what the bugfix is?

Yes and yes.

Specifically, I was asked to name the build directory in our build
system "workspace.o" (or something else ending in .o) because that
causes the automated backup to skip backing up temporary build

Does the backup not know about the NODUMP flag, aka chattr +d ?

I don't know. I'll follow up with the team that handles the
infrastructure. I believe there's some file access over NFS involved
here, and I am not sure if the NODUMP flag would be available via NFS.

Regards,
-Markus