When creating backend data for certain streams, fruit initially opens an internal "fake-fd" (a pipe() fd). Unfortunately when closing these fake-fds, it calls into SMB_VFS_NEXT_CLOSE() which will lead to strange results with virtual filesystems like vfs_cephfs. Have fix, need bugnumber.
This bug was referenced in samba master: 8f057333466b2d9845cd8bc2b794d98252ade2a4 719c83b4dc4cef16429ec2803621039545f6885e 40e70cbd3c3a1df9205a7b18d07784c1754cc340 36eb30fd7d4b82bffd0e1ab471c088f678d700a4 c5da08422990dfc1e082bc01aa10d6e415eebe3f 564b62a6f7c0a9b9712946d723118122b9c3785f
Created attachment 16387 [details] git-am fix for 4.13.next. Ralph, please check. Patch was back-ported from what went into master. Do we also need this for 4.12.next ?
Comment on attachment 16387 [details] git-am fix for 4.13.next. s4:torture/fruit: avoid sleep(10000000); if write_stream() fails should not be part of the patchset.
Created attachment 16388 [details] Patch for 4.12 backported from master
Created attachment 16389 [details] Patch for 4.13 backported from master
Thanks Ralph ! Re-assigning to Karolin for inclusion in 4.13.next, 4.12.next.
(In reply to Jeremy Allison from comment #6) Pushed to autobuild-v4-{13,12}-test.
This bug was referenced in samba v4-12-test: 83bd07f3806d212a3051e02897fdceb36557d78b cbdd15c13aa89834b11dc5ec9c6f23cdab692aeb 1bd5ffc109b426903aca8bb913dc504e3e8dbb0d 00b37ef3cdf78236dbd2289e702a3fca89dba1a6 8a77dcd69358a3f16ae7a93f9e7f606967ab2951 121fbf80523e4456a0fc068e08b0e6379d39200d
This bug was referenced in samba v4-13-test: a01b3646a540fb982c661a2550c5bfb49f62aa2f 15e4e106fe4c5a2310151dc4f88f25216306fa96 124a7dc068045362428dada609a41162455a6ff5 800a3dae9126bcacdc0b21f0b71dc38d94e3faa9 0391c7b55ff2810cbd3847700bf2183d86167d14 fdeba3944443ac7d7488413f252d8b4b2efe0485
This bug was referenced in samba v4-12-stable (Release samba-4.12.11): 83bd07f3806d212a3051e02897fdceb36557d78b cbdd15c13aa89834b11dc5ec9c6f23cdab692aeb 1bd5ffc109b426903aca8bb913dc504e3e8dbb0d 00b37ef3cdf78236dbd2289e702a3fca89dba1a6 8a77dcd69358a3f16ae7a93f9e7f606967ab2951 121fbf80523e4456a0fc068e08b0e6379d39200d
Closing out bug report. Thanks!
This bug was referenced in samba v4-13-stable (Release samba-4.13.4): a01b3646a540fb982c661a2550c5bfb49f62aa2f 15e4e106fe4c5a2310151dc4f88f25216306fa96 124a7dc068045362428dada609a41162455a6ff5 800a3dae9126bcacdc0b21f0b71dc38d94e3faa9 0391c7b55ff2810cbd3847700bf2183d86167d14 fdeba3944443ac7d7488413f252d8b4b2efe0485