It seems the patches for bug https://bugzilla.samba.org/show_bug.cgi?id=15126 cause a regression. We need a full stackbacktrace to analyse this.
This bug was referenced in samba master: 3dcdab86f13fabb7a8c6ce71c59a565287d11244 201e1969bf31af07e8bd52876ff7f4d72b48a848 3a37e4155c3cd82388652f89b611f2c46fee8525
Created attachment 17505 [details] Patch for 4.17 cherry-picked from master
Fwiw, the patch for 4.16 currently running in a pipeline in gitlab CI: https://gitlab.com/samba-team/devel/samba/-/pipelines/630008933 The core change is quite different, so the patches needs additional CI testing and review.
Created attachment 17508 [details] Patch for 4.15 and 4.16 backported from master
Reassigning to Jule for inclusion in 4.15, 4.16 and 4.17.
Pushed to autobuild-v4-{17,16,15}-test.
This bug was referenced in samba v4-15-test: c5796b0c7a35f2cc96cab3c63502c21b6153abd8 fa6012b63ab36704dfcfd6f95958ae0e089a94b5 6b5792b0a2ca1b7d4114272165968aaea673fceb
This bug was referenced in samba v4-17-test: 3139a1063a07ddb8a0df705bdc67d179969960b2 930380d4746f57e3d8ae9b6e9b9e37fc12ad890d ed1d01126160d49aea9088805120f95050510fe6
This bug was referenced in samba v4-16-test: b807f3624d1f720ad3d60c7ee51a69d89183633f 7c83b7788ec022551a2fd9381a1a5ff8e4adf5bc 1761ad3dff2e887593a06a9d9d47828427133bfd
This bug was referenced in samba v4-17-stable (Release samba-4.17.0rc5): 3139a1063a07ddb8a0df705bdc67d179969960b2 930380d4746f57e3d8ae9b6e9b9e37fc12ad890d ed1d01126160d49aea9088805120f95050510fe6
Closing out bug report. Thanks!
This bug was referenced in samba v4-16-stable (Release samba-4.16.5): b807f3624d1f720ad3d60c7ee51a69d89183633f 7c83b7788ec022551a2fd9381a1a5ff8e4adf5bc 1761ad3dff2e887593a06a9d9d47828427133bfd
This bug was referenced in samba v4-15-stable (Release samba-4.15.10): c5796b0c7a35f2cc96cab3c63502c21b6153abd8 fa6012b63ab36704dfcfd6f95958ae0e089a94b5 6b5792b0a2ca1b7d4114272165968aaea673fceb