1 POHMELFS network protocol.
3 Basic structure used in network communication is following command:
7 __u16 cmd; /* Command number */
8 __u16 csize; /* Attached crypto information size */
9 __u16 cpad; /* Attached padding size */
10 __u16 ext; /* External flags */
11 __u32 size; /* Size of the attached data */
12 __u32 trans; /* Transaction id */
13 __u64 id; /* Object ID to operate on. Used for feedback.*/
14 __u64 start; /* Start of the object. */
15 __u64 iv; /* IV sequence */
19 Commands can be embedded into transaction command (which in turn has own command),
20 so one can extend protocol as needed without breaking backward compatibility as long
21 as old commands are supported. All string lengths include tail 0 byte.
23 All commans are transfered over the network in big-endian. CPU endianess is used at the end peers.
25 @cmd - command number, which specifies command to be processed. Following
26 commands are used currently:
28 NETFS_READDIR = 1, /* Read directory for given inode number */
29 NETFS_READ_PAGE, /* Read data page from the server */
30 NETFS_WRITE_PAGE, /* Write data page to the server */
31 NETFS_CREATE, /* Create directory entry */
32 NETFS_REMOVE, /* Remove directory entry */
33 NETFS_LOOKUP, /* Lookup single object */
34 NETFS_LINK, /* Create a link */
35 NETFS_TRANS, /* Transaction */
36 NETFS_OPEN, /* Open intent */
37 NETFS_INODE_INFO, /* Metadata cache coherency synchronization message */
38 NETFS_PAGE_CACHE, /* Page cache invalidation message */
39 NETFS_READ_PAGES, /* Read multiple contiguous pages in one go */
40 NETFS_RENAME, /* Rename object */
41 NETFS_CAPABILITIES, /* Capabilities of the client, for example supported crypto */
42 NETFS_LOCK, /* Distributed lock message */
43 NETFS_XATTR_SET, /* Set extended attribute */
44 NETFS_XATTR_GET, /* Get extended attribute */
46 @ext - external flags. Used by different commands to specify some extra arguments
47 like partial size of the embedded objects or creation flags.
49 @size - size of the attached data. For NETFS_READ_PAGE and NETFS_READ_PAGES no data is attached,
50 but size of the requested data is incorporated here. It does not include size of the command
51 header (struct netfs_cmd) itself.
53 @id - id of the object this command operates on. Each command can use it for own purpose.
55 @start - start of the object this command operates on. Each command can use it for own purpose.
57 @csize, @cpad - size and padding size of the (attached if needed) crypto information.
59 Command specifications.
62 This command is used to sync content of the remote dir to the client.
64 @ext - length of the path to object.
66 @id - local inode number of the directory to read.
71 This command is used to read data from remote server.
72 Data size does not exceed local page cache size.
75 @start - first byte offset.
76 @size - number of bytes to read plus length of the path to object.
77 @ext - object path length.
81 Used to create object.
82 It does not require that all directories on top of the object were
83 already created, it will create them automatically. Each object has
84 associated @netfs_path_entry data structure, which contains creation
85 mode (permissions and type) and length of the name as long as name itself.
88 @size - size of the all data structures needed to create a path
89 @id - local inode number
94 Used to remove object.
96 @ext - length of the path to object.
98 @id - local inode number.
103 Lookup information about object on server.
105 @ext - length of the path to object.
107 @id - local inode number of the directory to look object in.
108 @start - local inode number of the object to look at.
112 Create hard of symlink.
113 Command is sent as "object_path|target_path".
115 @size - size of the above string.
116 @id - parent local inode number.
117 @start - 1 for symlink, 0 for hardlink.
118 @ext - size of the "object_path" above.
124 @size - incorporates all embedded command sizes including theirs header sizes.
125 @start - transaction generation number - unique id used to find transaction.
126 @ext - transaction flags. Unused at the moment.
131 Open intent for given transaction.
133 @id - local inode number.
135 @size - path length to the object.
136 @ext - open flags (O_RDWR and so on).
140 Metadata update command.
141 It is sent to servers when attributes of the object are changed and received
142 when data or metadata were updated. It operates with the following structure:
144 struct netfs_inode_info
150 unsigned int blocksize;
151 unsigned int padding;
159 It effectively mirrors stat(2) returned data.
162 @ext - path length to the object.
163 @size - the same plus size of the netfs_inode_info structure.
164 @id - local inode number.
169 Command is only received by clients. It contains information about
170 page to be marked as not up-to-date.
172 @id - client's inode number.
173 @start - last byte of the page to be invalidated. If it is not equal to
174 current inode size, it will be vmtruncated().
180 Used to read multiple contiguous pages in one go.
182 @start - first byte of the contiguous region to read.
183 @size - contains of two fields: lower 8 bits are used to represent page cache shift
184 used by client, another 3 bytes are used to get number of pages.
185 @id - local inode number.
186 @ext - path length to the object.
190 Used to rename object.
191 Attached data is formed into following string: "old_path|new_path".
193 @id - local inode number.
194 @start - parent inode number.
195 @size - length of the above string.
196 @ext - length of the old path part.
200 Used to exchange crypto capabilities with server.
201 If crypto capabilities are not supported by server, then client will disable it
202 or fail (if 'crypto_fail_unsupported' mount options was specified).
204 @id - superblock index. Used to specify crypto information for group of servers.
205 @size - size of the attached capabilities structure.
211 Used to send lock request/release messages. Although it sends byte range request
212 and is capable of flushing pages based on that, it is not used, since all Linux
213 filesystems lock the whole inode.
215 @id - lock generation number.
216 @start - start of the locked range.
217 @size - size of the locked range.
218 @ext - lock type: read/write. Not used actually. 15'th bit is used to determine,
219 if it is lock request (1) or release (0).
223 Used to set/get extended attributes for given inode.
224 @id - attribute generation number or xattr setting type
225 @start - size of the attribute (request or attached)
226 @size - name length, path len and data size for given attribute
227 @ext - path length for given object