diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2012-03-10 11:23:15 -0500 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2012-03-10 11:54:36 -0500 |
| commit | ad1e3968292e3af1c49ccbd0fb7d2674010f8efc (patch) | |
| tree | 5eee458017d2deeff73c27740d1bddd742a05990 /block | |
| parent | 4fc8796d23819da814ec25b7793bde8f104f1a2a (diff) | |
| download | linux-exynos-ad1e3968292e3af1c49ccbd0fb7d2674010f8efc.tar.gz linux-exynos-ad1e3968292e3af1c49ccbd0fb7d2674010f8efc.tar.bz2 linux-exynos-ad1e3968292e3af1c49ccbd0fb7d2674010f8efc.zip | |
NFSv4.0: Re-establish the callback channel on NFS4ERR_CB_PATHDOWN
When the NFSv4.0 server tells us that it can no-longer talk to us
on the callback channel, we should attempt a new SETCLIENTID in
order to re-transmit the callback channel information.
Note that as long as we do not change the boot verifier, this is
a safe procedure; the server is required to keep our state.
Also move the function nfs_handle_cb_pathdown to fs/nfs/nfs4state.c,
and change the name in order to mark it as being specific to NFSv4.0.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions