linux-stable.git/fs/nfs/flexfilelayout, branch linux-4.3.y

NFSv4.1/flexfiles: Clean up ff_layout_write_done_cb/ff_layout_commit_done_cb

2015-09-02T22:24:54+00:00

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Mark the layout for return in ff_layout_io_track_ds_error()

2015-09-02T22:24:26+00:00

When I/O cannot complete due to a fatal error on the DS, ensure that we
invalidate the corresponding layout segment and return it.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Mark layout for return if the mirrors are invalid

2015-09-01T22:12:11+00:00

If a read-write layout has an invalid mirror, then we should
mark it as invalid, and return it.
If a read-only layout has an invalid mirror, then mark it as invalid
and check if there is still at least one valid mirror before we return
it.

Note: Also fix incorrect use of pnfs_generic_mark_devid_invalid().
We really want nfs4_mark_deviceid_unavailable().

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: RW layouts are valid only if all mirrors are valid

2015-09-01T22:12:11+00:00

Unlike read layouts, the writeable layout cannot fall back to using only
one of the mirrors. It need to write to all of them.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Fix incorrect usage of pnfs_generic_mark_devid_invalid()

2015-09-01T22:12:11+00:00

Unlike the files layout, flexfiles does not test for the NFS_DEVICEID_INVALID
flag. Instead it relies on NFS_DEVICEID_UNAVAILABLE.
Fix is to replace with nfs4_mark_deviceid_unavailable().

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Fix freeing of mirrors

2015-09-01T19:18:57+00:00

Mirrors are now shared objects, so we should not be freeing them directly
inside ff_layout_free_lseg(). We should already be doing the right thing
in _ff_layout_free_lseg(), so just let it handle things.

Also ensure that ff_layout_free_mirror() frees the RPC credential if it
is set.

Fixes: 28a0d72c6867 ("Add refcounting to struct nfs4_ff_layout_mirror")
Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Don't mark the entire deviceid as bad for file errors

2015-08-30T20:10:27+00:00

If the file was fenced and/or has been deleted on the DS, then we want
to retry pNFS after a layoutreturn with error report. If the server
cannot fix the problem, then we rely on it to tell us so in the
response to the LAYOUTGET.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Fix a protocol error in layoutreturn

2015-08-28T00:42:20+00:00

According to the flexfiles protocol, the layoutreturn should specify an
array of errors in the following format:

struct ff_ioerr4 {
	offset4        ffie_offset;
	length4        ffie_length;
	stateid4       ffie_stateid;
	device_error4  ffie_errors<>;
};

This patch fixes up the code to ensure that our ffie_errors is indeed
encoded as an array (albeit with only a single entry).

Reported-by: Tom Haynes 
Cc: stable@vger.kernel.org
Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Allow coalescing of new layout segments and existing ones

2015-08-25T23:42:43+00:00

In order to ensure atomicity of updates, we merge the old layout segments
into the new ones, and then invalidate the old ones.

Also ensure that we order the list of layout segments so that
RO segments are preferred over RW.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfile: ff_layout_remove_mirror can be static

2015-08-25T18:40:09+00:00

Signed-off-by: Fengguang Wu 
Signed-off-by: Trond Myklebust