| commit | b5a635fb0ab0967e375281dd003cd7eb123f73fd | |
| author | David Disseldorp <ddiss@samba.org> | |
| Thu, 12 Feb 2015 09:58:20 +0000 (12 10:58 +0100) | ||
| committer | Jeremy Allison <jra@samba.org> | |
| Mon, 9 Mar 2015 20:27:07 +0000 (9 21:27 +0100) | ||
| tree | 996634db5873b1856789e6bed3e56abcbb1ddfc6 | treesnapshot (tar.gz zip) |
| parent | 1359e859328567090bf80911083605e17fbd4519 | commitdiff |
idl/ioctl: change QAR response array to a DATA_BLOB
[MS-FSCC] specifies:
The number of FILE_ALLOCATED_RANGE_BUFFER elements returned is
computed by dividing the size of the returned output buffer (from
either SMB or SMB2, the lower-layer protocol that carries the FSCTL)
by the size of the FILE_ALLOCATED_RANGE_BUFFER element.
Ideally, this requirement could be defined in idl with the following:
[flag(NDR_REMAINING)] file_alloced_range_buf array[];
However, this is not currently supported by PIDL, so just use an opaque
data blob for now.
Signed-off-by: David Disseldorp <ddiss@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
[MS-FSCC] specifies:
The number of FILE_ALLOCATED_RANGE_BUFFER elements returned is
computed by dividing the size of the returned output buffer (from
either SMB or SMB2, the lower-layer protocol that carries the FSCTL)
by the size of the FILE_ALLOCATED_RANGE_BUFFER element.
Ideally, this requirement could be defined in idl with the following:
[flag(NDR_REMAINING)] file_alloced_range_buf array[];
However, this is not currently supported by PIDL, so just use an opaque
data blob for now.
Signed-off-by: David Disseldorp <ddiss@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
| librpc/idl/ioctl.idl | diffblobblamehistory | |
| source4/torture/smb2/ioctl.c | diffblobblamehistory |