OK, that confirms my suspicion that the upstream bug referenced in the original description does not (entirely) relate to this issue.
I was able to confirm a few things:
- This bug is reproducible in hirsute as well, which means that the latest version of samba in our repositories (2:4.13.3+dfsg-1, at the time of this writing) doesn't have the fix.
- I was also able to reproduce this on a Fedora 33 VM.
The next steps would be to try to reproduce this with the latest version of samba on git.samba.org, and file an upstream bug if successful.
Thank you for your reply.
OK, that confirms my suspicion that the upstream bug referenced in the original description does not (entirely) relate to this issue.
I was able to confirm a few things:
- This bug is reproducible in hirsute as well, which means that the latest version of samba in our repositories (2:4.13.3+dfsg-1, at the time of this writing) doesn't have the fix.
- I was also able to reproduce this on a Fedora 33 VM.
The next steps would be to try to reproduce this with the latest version of samba on git.samba.org, and file an upstream bug if successful.