Project

General

Profile

Actions

Bug #11829

closed

ODX copy error with misaligned file size

Added by Gordon Ross over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

Description:
Noticed while testing something on Win2016:

When doing a copy/paste within a share on Win2016,
the client will use ODX_READ/ODX_WRITE. That all
appears to work OK, but on the last ODX write in the
sequence, NS returns STATUS_INVALID_PARAMETER.
It looks like this may have to do with the previous
ODX write returning a transfer size that's limited to
the size of the file, which happens to be not an even
multiple of the block size.

Steps to Reproduce:
Map an NS share on a Win2016 client.
Copy a file into the share, making sure to choose one
with length that's not an even multiple of 512.
Start a network capture
Use explorer to copy/paste within the same share.
Examine the network capture, looking at the last ODX write.
The status invalid parameter is not expected.

The file copy appears to be successful,
but the protocol error is not expected.

Actual Results:
See status invaild paramter, i.e.
frame 102 in the attached odx1.snoop


Files

odx1.snoop (595 KB) odx1.snoop Gordon Ross, 2019-10-16 07:33 PM
odx3.snoop (595 KB) odx3.snoop Gordon Ross, 2019-10-16 07:33 PM
Actions

Also available in: Atom PDF