BMC/Intel-BMC/linux.git/fs/cifs/cifspdu.h, branch dev

Add reflink copy over SMB3.11 with new FSCTL_DUPLICATE_EXTENTS

2015-06-29T02:15:38+00:00

Getting fantastic copy performance with cp --reflink over SMB3.11 using the new FSCTL_DUPLICATE_EXTENTS. This FSCTL was added in the SMB3.11 dialect (testing was against REFS file system) so have put it as a 3.11 protocol specific operation ("vers=3.1.1" on the mount). Tested at the SMB3 plugfest in Redmond. It depends on the new FS Attribute (BLOCK_REFCOUNTING) which is used to advertise support for the ability to do this ioctl (if you can support multiple files pointing to the same block than this refcounting ability or equivalent is needed to support the new reflink-like duplicate extent SMB3 ioctl. Signed-off-by: Steve French

add struct FILE_STANDARD_INFO

2015-06-28T03:25:56+00:00

Signed-off-by: Gregor Beck Reviewed-by: Jeff Layton

Add missing definitions for CIFS File System Attributes

2014-08-13T04:47:14+00:00

Signed-off-by: Steve French Acked-by: Shirish Pargaonkar

cifs: Use data structures to compute NTLMv2 response offsets

2013-11-11T22:58:11+00:00

A bit of cleanup plus some gratuitous variable renaming. I think using structures instead of numeric offsets makes this code much more understandable. Also added a comment about current time range expected by the server. Acked-by: Jeff Layton Reviewed-by: Shirish Pargaonkar Signed-off-by: Tim Gardner Signed-off-by: Steve French

Allow setting per-file compression via CIFS protocol

2013-11-02T17:52:44+00:00

An earlier patch allowed setting the per-file compression flag "chattr +c filename" on an smb2 or smb3 mount, and also allowed lsattr to return whether a file on a cifs, or smb2/smb3 mount was compressed. This patch extends the ability to set the per-file compression flag to the cifs protocol, which uses a somewhat different IOCTL mechanism than SMB2, although the payload (the flags stored in the compression_state) are the same. Reviewed-by: Jeff Layton Signed-off-by: Steve French

cifs: Make big endian multiplex ID sequences monotonic on the wire

2013-11-02T17:51:53+00:00

The multiplex identifier (MID) in the SMB header is only ever used by the client, in conjunction with PID, to match responses from the server. As such, the endianess of the MID is not important. However, When tracing packet sequences on the wire, protocol analyzers such as wireshark display MID as little endian. It is much more informative for the on-the-wire MID sequences to match debug information emitted by the CIFS driver. Therefore, one should write and read MID in the SMB header assuming it is always little endian. Observed from wireshark during the protocol negotiation and session setup: Multiplex ID: 256 Multiplex ID: 256 Multiplex ID: 512 Multiplex ID: 512 Multiplex ID: 768 Multiplex ID: 768 After this patch on-the-wire MID values begin at 1 and increase monotonically. Introduce get_next_mid64() for the internal consumers that use the full 64 bit multiplex identifier. Introduce the helpers get_mid() and compare_mid() to make the endian translation clear. Reviewed-by: Jeff Layton Signed-off-by: Tim Gardner Signed-off-by: Steve French

Query file system attributes from server on SMB2, not just cifs, mounts

2013-10-28T14:22:55+00:00

Currently SMB2 and SMB3 mounts do not query the file system attributes from the server at mount time as is done for cifs. These can be useful for debugging. Signed-off-by: Steve French

do not treat non-symlink reparse points as valid symlinks

2013-10-06T02:54:18+00:00

Windows 8 and later can create NFS symlinks (within reparse points) which we were assuming were normal NTFS symlinks and thus reporting corrupt paths for. Add check for reparse points to make sure that they really are normal symlinks before we try to parse the pathname. We also should not be parsing other types of reparse points (DFS junctions etc) as if they were a symlink so return EOPNOTSUPP on those. Also fix endian errors (we were not parsing symlink lengths as little endian). This fixes commit d244bf2dfbebfded05f494ffd53659fa7b1e32c1 which implemented follow link for non-Unix CIFS mounts CC: Stable Reviewed-by: Andrew Bartlett Signed-off-by: Steve French

[CIFS] Remove ext2 flags that have been moved to fs.h

2013-09-25T23:58:13+00:00

These flags were unused by cifs and since the EXT flags have been moved to common code in uapi/linux/fs.h we won't need to have a cifs specific copy. Signed-off-by: Steve French

CIFS: Implement follow_link for nounix CIFS mounts

2013-09-08T19:27:41+00:00

by using a query reparse ioctl request. Acked-by: Jeff Layton Signed-off-by: Pavel Shilovsky Signed-off-by: Steve French