Blame - Documentation/filesystems/nfs/nfs41-server.txt - LeafOS-Devices/android_kernel_samsung_gta4xl

2009-04-03 08:29:20 +0300

[diff] [blame]

1

NFSv4.1 Server Implementation

2

3

Server support for minorversion 1 can be controlled using the

4

/proc/fs/nfsd/versions control file. The string output returned

5

by reading this file will contain either "+4.1" or "-4.1"

6

correspondingly.

7

8

Currently, server support for minorversion 1 is disabled by default.

9

It can be enabled at run time by writing the string "+4.1" to

10

the /proc/fs/nfsd/versions control file. Note that to write this

11

control file, the nfsd service must be taken down. Use your user-mode

12

nfs-utils to set this up; see rpc.nfsd(8)

13

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

14

(Warning: older servers will interpret "+4.1" and "-4.1" as "+4" and

15

"-4", respectively. Therefore, code meant to work on both new and old

16

kernels must turn 4.1 on or off *before* turning support for version 4

17

on or off; rpc.nfsd does this correctly.)

18

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

19

The NFSv4 minorversion 1 (NFSv4.1) implementation in nfsd is based

J. Bruce Fields

73834d6

2010-01-20 17:17:04 -0500

[diff] [blame]

20

on RFC 5661.

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

21

22

From the many new features in NFSv4.1 the current implementation

23

focuses on the mandatory-to-implement NFSv4.1 Sessions, providing

24

"exactly once" semantics and better control and throttling of the

25

resources allocated for each client.

26

27

Other NFSv4.1 features, Parallel NFS operations in particular,

28

are still under development out of tree.

29

See http://wiki.linux-nfs.org/wiki/index.php/PNFS_prototype_design

30

for more information.

31

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

32

The current implementation is intended for developers only: while it

33

does support ordinary file operations on clients we have tested against

34

(including the linux client), it is incomplete in ways which may limit

35

features unexpectedly, cause known bugs in rare cases, or cause

36

interoperability problems with future clients. Known issues:

37

38

- gss support is questionable: currently mounts with kerberos

39

from a linux client are possible, but we aren't really

40

conformant with the spec (for example, we don't use kerberos

41

on the backchannel correctly).

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

42

- Incomplete backchannel support: incomplete backchannel gss

43

support and no support for BACKCHANNEL_CTL mean that

44

callbacks (hence delegations and layouts) may not be

45

available and clients confused by the incomplete

46

implementation may fail.

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

47

- We do not support SSV, which provides security for shared

48

client-server state (thus preventing unauthorized tampering

49

with locks and opens, for example). It is mandatory for

50

servers to support this, though no clients use it yet.

51

- Mandatory operations which we do not support, such as

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

52

DESTROY_CLIENTID, are not currently used by clients, but will be

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

53

(and the spec recommends their uses in common cases), and

54

clients should not be expected to know how to recover from the

55

case where they are not supported. This will eventually cause

56

interoperability failures.

57

58

In addition, some limitations are inherited from the current NFSv4

59

implementation:

60

61

- Incomplete delegation enforcement: if a file is renamed or

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

62

unlinked by a local process, a client holding a delegation may

63

continue to indefinitely allow opens of the file under the old

64

name.

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

65

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

66

The table below, taken from the NFSv4.1 document, lists

67

the operations that are mandatory to implement (REQ), optional

68

(OPT), and NFSv4.0 operations that are required not to implement (MNI)

69

in minor version 1. The first column indicates the operations that

70

are not supported yet by the linux server implementation.

71

72

The OPTIONAL features identified and their abbreviations are as follows:

73

pNFS Parallel NFS

74

FDELG File Delegations

75

DDELG Directory Delegations

76

77

The following abbreviations indicate the linux server implementation status.

78

I Implemented NFSv4.1 operations.

79

NS Not Supported.

80

NS* unimplemented optional feature.

81

P pNFS features implemented out of tree.

82

PNS pNFS features that are not supported yet (out of tree).

Operations

+----------------------+------------+--------------+----------------+

87

88

89

| | MNI | or OPT) | |

90

+----------------------+------------+--------------+----------------+

91

92

NS | BACKCHANNEL_CTL | REQ | | Section 18.33 |

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

93

I | BIND_CONN_TO_SESSION | REQ | | Section 18.34 |

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

I | CREATE_SESSION | REQ | | Section 18.36 |

| | | (REQ) | |

NS | DESTROY_CLIENTID | REQ | | Section 18.50 |

103

I | DESTROY_SESSION | REQ | | Section 18.37 |

104

I | EXCHANGE_ID | REQ | | Section 18.35 |

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

105

I | FREE_STATEID | REQ | | Section 18.38 |

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

NS*| OPENATTR | OPT | | Section 18.17 |

123

| OPEN_CONFIRM | MNI | | N/A |

J. Bruce Fields

2010-04-19 15:11:28 -0400

[diff] [blame]

131

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

132

| RELEASE_LOCKOWNER | MNI | | N/A |

133

134

135

| RENEW | MNI | | N/A |

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

139

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

140

141

I | SEQUENCE | REQ | | Section 18.46 |

142

143

| SETCLIENTID | MNI | | N/A |

144

| SETCLIENTID_CONFIRM | MNI | | N/A |

145

NS | SET_SSV | REQ | | Section 18.47 |

J. Bruce Fields

2011-07-18 18:40:21 -0400

[diff] [blame]

146

I | TEST_STATEID | REQ | | Section 18.48 |

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

Callback Operations

+-------------------------+-----------+-------------+---------------+

154

155

156

| | MNI | or OPT) | |

157

+-------------------------+-----------+-------------+---------------+

NS*| CB_NOTIFY_LOCK | OPT | | Section 20.11 |

| | | (REQ) | |

| | | (REQ) | |

NS | CB_RECALL_SLOT | REQ | | Section 20.8 |

| | | (REQ) | |

| | | (REQ) | |

| | | (REQ) | |

+-------------------------+-----------+-------------+---------------+

180

181

Implementation notes:

182

J. Bruce Fields

2009-09-20 17:01:33 -0400

[diff] [blame]

183

DELEGPURGE:

184

* mandatory only for servers that support CLAIM_DELEGATE_PREV and/or

185

CLAIM_DELEG_PREV_FH (which allows clients to keep delegations that

186

persist across client reboots). Thus we need not implement this for

187

now.

188

Benny Halevy

2009-04-03 08:29:20 +0300

[diff] [blame]

189

EXCHANGE_ID:

190

* only SP4_NONE state protection supported

191

* implementation ids are ignored

192

193

CREATE_SESSION:

194

* backchannel attributes are ignored

195

* backchannel security parameters are ignored

196

197

SEQUENCE:

198

* no support for dynamic slot table renegotiation (optional)

199

Andy Adamson

ddc04fd

2009-09-23 21:32:21 -0400

[diff] [blame]

200

Nonstandard compound limitations:

201

* No support for a sessions fore channel RPC compound that requires both a

202

ca_maxrequestsize request and a ca_maxresponsesize reply, so we may

203

fail to live up to the promise we made in CREATE_SESSION fore channel

204

negotiation.

205

* No more than one IO operation (read, write, readdir) allowed per

206

compound.

J. Bruce Fields