OS X 10.9.5 and 10.10.2 clients crash when copying file with resource fork to server. 

The file is an Photoshop image with a large resource fork. I'm enabling named streams support in Samba and tested with fruit/streams_xattr and streams_depot, both result in the same crash.

Seems to always happen at a point where we returned streaminfo for the fully copied file. Sometimes there's a subsequent strange stream open where the client requests the  "AFP_Resource" stream on the *base directory, which doesn't make sense at all and indicated that at this point something went wrong.

Other traces show the last response is exactly the streaminfo.

Tested with Samba 4.2.0, 4.2.2 and master. I was initially suspecting the recent compound response padding changeset introduce a regression, but this is reproducible with vanilla 4.2.0.

This works fine against a Windows or Mac SMB server.

smb.conf:
[global]
    server role = standalone
    log file = /var/log/samba.log
    debug pid = yes
    log level = 1
    store dos attributes = yes
    read only = no
    ea support = yes
    idmap config * : backend = tdb
    idmap config * : range = 10000-20000
    smb2 leases = yes
    kernel change notify = no
    fruit:nfs_aces = no
    fruit:aapl = no

[fruit]
    path = /Volumes/streams
    vfs objects = catia fruit streams_xattr acl_xattr 

[depot]
    path = /Volumes/streams
    vfs objects = streams_depot acl_xattr