When processing an SMB2 CREATE requests on the quote fake file "$Extend/$Quota" we end up calling into the VFS with SMB_VFS_GET_DOSATTRIBUTES via fdos_mode(). Typically the VFS will have no idea what about this special quota related NTFS file and specifically vfs_gpfs will log an error message: vfs_gpfs_get_dos_attributes: Getting winattrs failed for $Extend/$Quota We must avoid hitting the VFS and prime the correct DOS attributes in fdos_mode(). While at it, fix the returned attributes (DOS attributes and timestamps) while at it. Have patch, need bugnumber.
This bug was referenced in samba master: 1e338d51602a7dca6108e5e8704f5cdde4740713 51b0fd0c566ff6bf112ab9752d9b105a6bb786a8 e093eaed1046638193d973c39fa9df74e41148d3 52a421111218d94d2e5cb131648bcdf5411d910b
Created attachment 16647 [details] Patch for 4.14 cherry-picked from master
Created attachment 16648 [details] Patch for 4.13 backported from master Patch 2/3 is new/different compared to what's in master. In master we're changing fdos_mode() function, checking fsp->fake_handle. In 4.13 we're still using path based dos_mode(), so the check has to be done differently. After reviewing, please remember to download the patch and add your reviewed-by to 2/3. Thanks!
Created attachment 16649 [details] Re-upload with my RB+ added for 4.13. LGTM. RB+.
Comment on attachment 16649 [details] Re-upload with my RB+ added for 4.13. Drat, patch 2/3 is missing bug URL.
Created attachment 16650 [details] Patch for 4.13 backported from master
Reassigning to Karolin for inclusion in 4.13 and 4.14..
(In reply to Ralph Böhme from comment #7) Pushed to autobuild-v4-{14,13}-test.
Pushed to the test branches and included in the last releases. Closing out bug report. Thanks!
(In reply to Karolin Seeger from comment #9) Please ignore, wrong bug report -> re-opening
This bug was referenced in samba v4-13-test: 7ecf16506616c7f3071c8c2206cfda17b7743351 a3dea8a0d088c7624c1a81a81873c96c068bcdbd 97c6d6fee8a133c2f647f9c588f863ab9c4e15c9
Pushed to v4-14-test. Closing out bug report. Thanks!
This bug was referenced in samba v4-14-test: 8abd1abca64bd9034482498484310692a411b9dd 7e1d4a4b1385b9bc75ce61531c8df77584bb9ead b53968656eee6c57e281ee32bff1d4643b4292f0 46995a8b14675f30536a65ceeaf687fa7cbedd9e
This bug was referenced in samba v4-14-stable (Release samba-4.14.7): 8abd1abca64bd9034482498484310692a411b9dd 7e1d4a4b1385b9bc75ce61531c8df77584bb9ead b53968656eee6c57e281ee32bff1d4643b4292f0 46995a8b14675f30536a65ceeaf687fa7cbedd9e
This bug was referenced in samba v4-13-stable (Release samba-4.13.11): 7ecf16506616c7f3071c8c2206cfda17b7743351 a3dea8a0d088c7624c1a81a81873c96c068bcdbd 97c6d6fee8a133c2f647f9c588f863ab9c4e15c9