Comment 38 for bug 2007055

Is there anything anyone would want to know (or must be told), so we can anticipate these kinds of issues with Linux/the Kernel/Mint/ReadyNAS/NetGear/Ubuntu/Debian/Synology/SAMBA/cifs in the future and prevent another regression ruining all my or any other users' timestamps next time we run a rsync backup on our NAS after a software update? Or is this just another case of "different interpretation of standards leading to potentially unwanted results"?

I'm not very familiar with the intricacies of Linux neither the respnsibilities of its software development community and release cycles, but if you want me to pass those findings (with a brief description of what exactly is happening, where and when) to anyone I'll try my best.

Because when you're saying "ubuntu 22 VM, which shows the issue with a server running an earlier version of Samba (4.7.x) and a later version", I understand this as "if things work as they should, we're somehow in a sweet spot within versions now and any update can break functionality again.". Which is not exactly something I'm looking forward to in an operating system.

Thanks for your support, highly appreciated.