| commit | 9b94de161f30bb34c666c0cf0cc94250e6a7b863 | |
| author | Jeremy Allison <jra@samba.org> | |
| Wed, 27 Mar 2013 18:54:34 +0000 (27 11:54 -0700) | ||
| committer | David Disseldorp <ddiss@samba.org> | |
| Tue, 2 Apr 2013 18:06:38 +0000 (2 20:06 +0200) | ||
| tree | f71928928b0d315591cf6b0cee0ee88ca53c93a0 | treesnapshot (tar.gz zip) |
| parent | 43becd6f305bd5d21d886027d38a92d4dff22d75 | commitdiff |
Final fix for bug #9130 - Certain xattrs cause Windows error 0x800700FF
The spec lies when it says that NextEntryOffset is the only value
considered when finding the next EA. We were adding 4 more extra
pad bytes than needed (i.e. if the next entry already was on a 4
byte boundary, then we were adding 4 additional pad bytes).
Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: David Disseldorp <ddiss@suse.de>
The spec lies when it says that NextEntryOffset is the only value
considered when finding the next EA. We were adding 4 more extra
pad bytes than needed (i.e. if the next entry already was on a 4
byte boundary, then we were adding 4 additional pad bytes).
Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: David Disseldorp <ddiss@suse.de>
| source3/smbd/trans2.c | diffblobblamehistory |