That command output should be fenced text; not a screenshot.

@Ramhound, yes. I tested it on Windows 11 22H4 yesterday.

Thanks for that. You're definitely correct about using the dedicated tool for the file - lslocks --json gives me good data, whereas cat /proc/locks would have been Hellish to parse.

Ah, your edit mostly answers that.

That seems like a markedly strange decision. Got any knowledge of why this is so, considering how important this information is?

Thanks. I've left the other answer as it's slightly better as an answer to the specific question I've asked, but this is the much more interesting one - which explains why it's like this. Many thanks. Perhaps it's not worth worrying about these values, then.

For future readers, see this VT result for posterity. It's definitely safe, but if in doubt, compile oneself.

Thanks. Perhaps it predates mobile phone numbers.