<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/nfs/client.c, branch linux-5.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-07-13T21:52:45Z</updated>
<entry>
<title>NFSv4.2: query the server for extended attribute support</title>
<updated>2020-07-13T21:52:45Z</updated>
<author>
<name>Frank van der Linden</name>
</author>
<published>2020-06-23T22:38:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b78ef845c35dbae25e57b598901a65b13d940c81'/>
<id>urn:sha1:b78ef845c35dbae25e57b598901a65b13d940c81</id>
<content type='text'>
Query the server for extended attribute support, and record it
as the NFS_CAP_XATTR flag in the server capabilities.

Signed-off-by: Frank van der Linden &lt;fllinden@amazon.com&gt;
Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
<entry>
<title>NFSv4.2: define limits and sizes for user xattr handling</title>
<updated>2020-07-13T21:52:45Z</updated>
<author>
<name>Frank van der Linden</name>
</author>
<published>2020-06-23T22:38:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=04a5da690e8f2da23c2ac940f2921e3aa622db82'/>
<id>urn:sha1:04a5da690e8f2da23c2ac940f2921e3aa622db82</id>
<content type='text'>
Set limits for extended attributes (attribute value size and listxattr
buffer size), based on the fs-independent limits (XATTR_*_MAX).

Define the maximum XDR sizes for the RFC 8276 XATTR operations.
In the case of operations that carry a larger payload (SETXATTR,
GETXATTR, LISTXATTR), these exclude that payload, which is added
as separate pages, like other operations do.

Define, much like for read and write operations, the maximum overhead
sizes for get/set/listxattr, and use them to limit the maximum payload
size for those operations, in combination with the channel attributes.

Signed-off-by: Frank van der Linden &lt;fllinden@amazon.com&gt;
Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
<entry>
<title>nfs: add minor version to nfs_server_key for fscache</title>
<updated>2020-02-25T18:53:24Z</updated>
<author>
<name>Scott Mayhew</name>
</author>
<published>2020-02-24T21:29:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=55dee1bc0d72877b99805e42e0205087e98b9edd'/>
<id>urn:sha1:55dee1bc0d72877b99805e42e0205087e98b9edd</id>
<content type='text'>
An NFS client that mounts multiple exports from the same NFS
server with higher NFSv4 versions disabled (i.e. 4.2) and without
forcing a specific NFS version results in fscache index cookie
collisions and the following messages:
[  570.004348] FS-Cache: Duplicate cookie detected

Each nfs_client structure should have its own fscache index cookie,
so add the minorversion to nfs_server_key.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=200145
Signed-off-by: Scott Mayhew &lt;smayhew@redhat.com&gt;
Signed-off-by: Dave Wysochanski &lt;dwysocha@redhat.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>NFS: allow deprecation of NFS UDP protocol</title>
<updated>2020-01-24T21:51:13Z</updated>
<author>
<name>Olga Kornievskaia</name>
</author>
<published>2019-12-16T21:34:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b24ee6c64ca785739b3ef8d95fd6becaad1bde39'/>
<id>urn:sha1:b24ee6c64ca785739b3ef8d95fd6becaad1bde39</id>
<content type='text'>
Add a kernel config CONFIG_NFS_DISABLE_UDP_SUPPORT to disallow NFS
UDP mounts and enable it by default.

Signed-off-by: Olga Kornievskaia &lt;kolga@netapp.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>NFS: Additional refactoring for fs_context conversion</title>
<updated>2020-01-15T15:15:17Z</updated>
<author>
<name>Scott Mayhew</name>
</author>
<published>2019-12-10T12:31:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=62a55d088cd87d480a6fd67b0d63b14ccae80838'/>
<id>urn:sha1:62a55d088cd87d480a6fd67b0d63b14ccae80838</id>
<content type='text'>
Split out from commit "NFS: Add fs_context support."

This patch adds additional refactoring for the conversion of NFS to use
fs_context, namely:

 (*) Merge nfs_mount_info and nfs_clone_mount into nfs_fs_context.
     nfs_clone_mount has had several fields removed, and nfs_mount_info
     has been removed altogether.
 (*) Various functions now take an fs_context as an argument instead
     of nfs_mount_info, nfs_fs_context, etc.

Signed-off-by: Scott Mayhew &lt;smayhew@redhat.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>NFS: rename nfs_fs_context pointer arg in a few functions</title>
<updated>2020-01-15T15:15:17Z</updated>
<author>
<name>Scott Mayhew</name>
</author>
<published>2019-12-10T12:31:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=38465f5d1af932494d66b52d26bb3a02b837cdf8'/>
<id>urn:sha1:38465f5d1af932494d66b52d26bb3a02b837cdf8</id>
<content type='text'>
Split out from commit "NFS: Add fs_context support."

Rename cfg to ctx in nfs_init_server(), nfs_verify_authflavors(),
and nfs_request_mount().  No functional changes.

Signed-off-by: Scott Mayhew &lt;smayhew@redhat.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>NFS: Rename struct nfs_parsed_mount_data to struct nfs_fs_context</title>
<updated>2020-01-15T15:15:17Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2019-12-10T12:31:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5eb005caf5383dd328199f0f2114cd7dad731d3d'/>
<id>urn:sha1:5eb005caf5383dd328199f0f2114cd7dad731d3d</id>
<content type='text'>
Rename struct nfs_parsed_mount_data to struct nfs_fs_context and rename
pointers to it to "ctx".  At some point this will be pointed to by an
fs_context struct's fs_private pointer.

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>nfs: don't pass nfs_subversion to -&gt;create_server()</title>
<updated>2020-01-15T15:15:16Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2019-12-10T12:31:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0c38f2131df9865aa9fb24b7ad30a9657588e0e1'/>
<id>urn:sha1:0c38f2131df9865aa9fb24b7ad30a9657588e0e1</id>
<content type='text'>
pick it from mount_info

Reviewed-by: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>NFSv4.1: Don't rebind to the same source port when reconnecting to the server</title>
<updated>2019-11-04T02:28:45Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2019-10-17T15:13:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e6237b6feb37582fbd6bd7a8336d1256a6b4b4f9'/>
<id>urn:sha1:e6237b6feb37582fbd6bd7a8336d1256a6b4b4f9</id>
<content type='text'>
NFSv2, v3 and NFSv4 servers often have duplicate replay caches that look
at the source port when deciding whether or not an RPC call is a replay
of a previous call. This requires clients to perform strange TCP gymnastics
in order to ensure that when they reconnect to the server, they bind
to the same source port.

NFSv4.1 and NFSv4.2 have sessions that provide proper replay semantics,
that do not look at the source port of the connection. This patch therefore
ensures they can ignore the rebind requirement.

Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
<entry>
<title>NFS/pnfs: Separate NFSv3 DS and MDS traffic</title>
<updated>2019-11-04T02:28:45Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2019-10-17T13:49:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=52f98f1a2ddd2bb561f2c7e3b19a81d816a63118'/>
<id>urn:sha1:52f98f1a2ddd2bb561f2c7e3b19a81d816a63118</id>
<content type='text'>
If a NFSv3 server is being used as both a DS and as a regular NFSv3 server,
we may want to keep the IO traffic on a separate TCP connection, since
it will typically have very different timeout characteristics.

This patch therefore sets up a flag to separate the two modes of operation
for the nfs_client.

Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
</feed>
