wireguard-linux/fs/nfs/direct.c, branch jd/unified-crypt-queue

NFS: Try to join page groups before an O_DIRECT retransmission

2020-04-01T17:37:57Z

If we have to retransmit requests, try to join their page groups first. Signed-off-by: Trond Myklebust

NFS: Fix a request reference leak in nfs_direct_write_clear_reqs()

2020-04-01T17:37:56Z

nfs_direct_write_scan_commit_list() will lock the request and bump the reference count, but we also need to account for the reference that was taken when we initially added the request to the commit list. Fixes: fb5f7f20cdb9 ("NFS: commit errors should be fatal") Signed-off-by: Trond Myklebust

NFS/pNFS: Clean up pNFS commit operations

2020-03-27T20:34:35Z

Move the pNFS commit related operations into a separate structure that can be carried by the pnfs_ds_commit_info. Signed-off-by: Trond Myklebust

NFS: Remove bucket array from struct pnfs_ds_commit_info

2020-03-27T20:34:35Z

Remove the unused bucket array in struct pnfs_ds_commit_info. Signed-off-by: Trond Myklebust

NFS: Fix O_DIRECT commit verifier handling

2020-03-27T20:34:34Z

Instead of trying to save the commit verifiers and checking them against previous writes, adopt the same strategy as for buffered writes, of just checking the verifiers at commit time. Signed-off-by: Trond Myklebust

NFS: commit errors should be fatal

2020-03-27T20:34:34Z

Fix the O_DIRECT code to avoid retries if the COMMIT fails with a fatal error. Signed-off-by: Trond Myklebust

NFS/pNFS: Allow O_DIRECT to release the DS commitinfo

2020-03-27T20:34:34Z

Add a pNFS callback to allow the O_DIRECT code to release the DS commitinfo when freeing the dreq. Signed-off-by: Trond Myklebust

NFSv4/pnfs: Support a list of commit arrays in struct pnfs_ds_commit_info

2020-03-27T20:34:34Z

When we have multiple layout segments with different lists of mirrored data, we need to track the commits on a per layout segment basis. This patch adds a list to support this tracking in struct pnfs_ds_commit_info. Signed-off-by: Trond Myklebust

NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails

2020-03-22T20:47:58Z

When dreq is allocated by nfs_direct_req_alloc(), dreq->kref is initialized to 2. Therefore we need to call nfs_direct_req_release() twice to release the allocated dreq. Usually it is called in nfs_file_direct_{read, write}() and nfs_direct_complete(). However, current code only calls nfs_direct_req_relese() once if nfs_get_lock_context() fails in nfs_file_direct_{read, write}(). So, that case would result in memory leak. Fix this by adding the missing call. Signed-off-by: Misono Tomohiro Signed-off-by: Trond Myklebust

NFS: Fix nfs_direct_write_reschedule_io()

2020-01-15T15:54:33Z

The 'hdr->good_bytes' is defined as the number of bytes we expect to read or write starting at offset hdr->io_start. In the case of a partial read/write we may end up adjusting hdr->args.offset and hdr->args.count to skip I/O for data that was already read/written, and so we must ensure the calculation takes that into account. Signed-off-by: Trond Myklebust Signed-off-by: Anna Schumaker