| commit | a0346c10974fd23a152b98783ba8975604dd3ea5 | |
| author | Jeremy Allison <jra@samba.org> | |
| Wed, 27 Mar 2013 18:54:34 +0000 (27 11:54 -0700) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Fri, 26 Apr 2013 07:25:03 +0000 (26 09:25 +0200) | ||
| tree | 1b5753259701a78c0b6fb935d54b2dd27c291509 | treesnapshot (tar.gz zip) |
| parent | 6c9f1394d1809a67a855bf2f98cdc2ac9dcf3f10 | 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>
The last 5 patches address bug #9130 - Certain xattrs cause Windows error
0x800700FF.
(cherry picked from commit 57db33599589b06a60cb7cbb454f87bf40c542e0)
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>
The last 5 patches address bug #9130 - Certain xattrs cause Windows error
0x800700FF.
(cherry picked from commit 57db33599589b06a60cb7cbb454f87bf40c542e0)
| source3/smbd/trans2.c | diffblobblamehistory |